Techniques for managing region build dependencies

ABSTRACT

Techniques are described for performing an automated region build. An orchestration service (e.g., a Multi-Flock Orchestrator (MFO)) may be configured to bootstrap any suitable number of services within a region corresponding to one or more data centers. Each service can be associated with a respective set of resources (e.g., infrastructure components to be provisioned, software artifacts to be deployed, etc.). The WO can obtain configuration files corresponding to the services to be bootstrapped and perform a static analysis the configuration files to identify one or more dependencies between the services. Circular dependencies can be identified and resolved before region build. A graph may be generated that maintains the dependencies identified and indicates a corresponding order with which bootstrapping tasks are to be performed. The WO may traverse the graph to incrementally instruct, according to the identified dependencies, a provisioning and deployment manager to bootstrap services in the region.

CROSS-REFERENCE TO RELATED APPLICATIONS

This non-provisional application claims priority to U.S. ProvisionalPatent Application No. 63/308,003, filed on Feb. 8, 2022, entitled“Techniques for Bootstrapping a Region Build,” U.S. Provisional PatentApplication No. 63/312,814, filed on Feb. 22, 2022, entitled “Techniquesfor Implementing Virtual Data Centers,” and U.S. Provisional PatentApplication No. 63/315,034, filed on Feb. 28, 2022, entitled “Techniquesfor Managing Region Build Dependencies,” the disclosures of which areherein incorporated by reference in their entirety for all purposes.

BACKGROUND

Today, cloud infrastructure services utilize many individual services tobuild a data center (e.g., to bootstrap various resources in a datacenter of a particular geographic region). In some examples, a region isa logical abstraction corresponding to a localized geographical area inwhich one or more data centers are (or are to be) located. Building adata center may include provisioning and configuring infrastructureresources and deploying code to those resources (e.g., for a variety ofservices). The operations for building a data center may be collectivelyreferred to as performing a “region build.” Any suitable number of datacenters may be included in a region and therefore a region build mayinclude operations for building multiple data centers. Conventionaltools for building a region require significant manual effort asbootstrapping operations for one service may depend on otherfunctionality and/or services of the region which may not yet beavailable. As the number of service teams and regions grows, the tasksperformed for orchestrating provisioning and deployment drasticallyincrease. Substantially relying on manual efforts for bootstrappingservices and/or building regions is time intensive, incurs risks, andmay not scale well.

BRIEF SUMMARY

Embodiments of the present disclosure relate to performing an automatedregion build (e.g., bootstrapping (e.g., provisioning and/or deploying)resources (e.g., infrastructure component, artifacts, etc.) for anysuitable number of services within a region (e.g., a geographicallocation associated with one or more data centers)). Dependenciesbetween bootstrapping operations can be automatically detected by aMulti-Flock Orchestrator (MFO) based at least in part on performing astatic analysis (e.g., parsing one or more times) of configuration filescorresponding to the services. The MFO may orchestrate bootstrappingoperations according to the dependencies it identified.

At least one embodiment is directed to a computer-implemented method.The method may include obtaining, by an orchestration service (e.g., amulti-flock orchestrator) of a cloud-computing environment, a pluralityof configuration files corresponding to a plurality of services to bebootstrapped to a region. In some embodiments, the plurality ofconfiguration files provide data from which bootstrapping tasks forbootstrapping the plurality of services within the region areidentifiable. The method may further include identifying, by theorchestration service, one or more dependencies between respectiveservices of the plurality of services based at least in part onexecuting operations for parsing the plurality of configuration files.The method may further include generating, orchestration service andbased at least in part on the parsing, a build dependency graph thatmaintains the one or more dependencies identified. In some embodiments,the build dependency graph may be a data structure that identifies theplurality of configuration files and the one or more dependencies andindicates a corresponding order with which bootstrapping tasks are to beperformed. The method may further include incrementally instructing, bythe orchestration service, a provisioning and deployment manager (e.g.,CIOS Central of FIGS. 1-3 ) to execute bootstrapping tasks based atleast in part on traversing the build dependency graph. In someembodiments, the bootstrapping tasks may be executed to cause theplurality of services to be bootstrapped to the region according to theone or more dependencies identified.

In some embodiments, identifying the one or more dependencies mayfurther include identifying, based at least in part on the parsing, arequired capability of a first service on which a second servicedepends. The build dependency graph as generated may indicate that thefirst service is to be bootstrapped before the second service and thatinitiation of respective bootstrapping tasks for the second service isto be delayed until a capability indicating the first service isbootstrapped is published. In some embodiments, identifying the one ormore dependencies may further include identifying, orchestration serviceand based at least in part on the parsing, an optional capability of thefirst service on which a second service optionally depends. The builddependency graph as generated may indicate that the second service maybe bootstrapped before the first service. In some embodiments, the builddependency graph further indicates that, if the second service isbootstrapped before the first service, additional bootstrapping taskscorresponding to the second service are to be executed when the firstservice is available.

In some embodiments, the method may further comprise identifying, by theorchestration service, a circular dependency between two services.Identifying the circular dependency may cause the orchestration serviceto instruct the provisioning and deployment manager to perform at leastone additional execution of respective bootstrapping tasks correspondingto at least one of the two services. In some embodiments, performing theat least one additional execution of the respective bootstrapping tasksresolves the circular dependency between the two services.

In some embodiments, the method may further comprise identifying, by theorchestration service, an orphaned service within the build dependencygraph. The build dependency graph may indicate that the orphaned servicewill not be bootstrapped due to an error with a correspondingconfiguration file corresponding to the orphaned service.

In some embodiments, the method may further comprise generating, by theorchestration service, a plurality of phase data structures identifyingone or more phases associated with bootstrapping the region and an orderby which the one or more phases are to be executed. Each phase datastructure may be associated with bootstrapping one or more instances ofa given service.

Another embodiment is directed to a computing device hosting anorchestration service of a cloud-computing system and comprising one ormore processors and instructions that, when executed by the one or moreprocessors, cause the orchestration service and/or the computing deviceto perform the method(s) disclosed herein.

Another embodiment is directed to a cloud-computing system comprisingone or more processors and instructions that, when executed by the oneor more processors, cause an orchestration service of thecloud-computing system to perform the method(s) disclosed herein.

Still another embodiment is directed to a non-transitorycomputer-readable medium storing computer-executable instructions that,when executed by one or more processors of a cloud-computing system,cause an orchestration service of the cloud-computing system to performthe method(s) disclosed herein.

BRIEF DESCRIPTION OF THE DRAWINGS

To easily identify the discussion of any particular element or act, themost significant digit or digits in a reference number refer to thefigure number in which that element is first introduced.

FIG. 1 is a block diagram of an environment in which a CloudInfrastructure Orchestration Service (CIOS) may operate to dynamicallyprovide bootstrap services in a region, according to at least oneembodiment.

FIG. 2 is a block diagram for illustrating an environment and method forbuilding a virtual bootstrap environment (ViBE), according to at leastone embodiment.

FIG. 3 is a block diagram for illustrating an environment and method forbootstrapping services to a target region utilizing the ViBE, accordingto at least one embodiment.

FIG. 4 is a block diagram depicting a region associated with a number offlocks (e.g., services), according to at least one embodiment.

FIG. 5 is a block diagram depicting a relationship between a flock, anumber of phases, and a corresponding number of execution targets foreach phase, according to at least one embodiment.

FIG. 6 is an example code segment illustrating a number of capabilitytypes, according to at least one embodiment.

FIG. 7 is another example code segments from which one or moredependencies may be identified, according to at least one embodiment.

FIG. 8 illustrates an example portion of a build dependency graph,according to at least one embodiment.

FIG. 9 illustrates an example method for performing bootstrapping anumber of services within a region based at least in part on one or moredependencies identified by executing a static analysis of one or moreflock configuration files, according to at least one embodiment.

FIG. 10 is a block diagram illustrating one pattern for implementing acloud infrastructure as a service system, according to at least oneembodiment.

FIG. 11 is a block diagram illustrating another pattern for implementinga cloud infrastructure as a service system, according to at least oneembodiment.

FIG. 12 is a block diagram illustrating another pattern for implementinga cloud infrastructure as a service system, according to at least oneembodiment.

FIG. 13 is a block diagram illustrating another pattern for implementinga cloud infrastructure as a service system, according to at least oneembodiment.

FIG. 14 is a block diagram illustrating an example computer system,according to at least one embodiment.

DETAILED DESCRIPTION

In the following description, for the purposes of explanation, specificdetails are set forth in order to provide a thorough understanding ofcertain embodiments. However, it will be apparent that variousembodiments may be practiced without these specific details. The figuresand description are not intended to be restrictive. The word “exemplary”is used herein to mean “serving as an example, instance, orillustration.” Any embodiment or design described herein as “exemplary”is not necessarily to be construed as preferred or advantageous overother embodiments or designs.

Example Automated Data Center Build (Region Build) Infrastructure

The adoption of cloud services has seen a rapid uptick in recent times.Various types of cloud services are now provided by various differentcloud service providers (CSPs). The term cloud service is generally usedto refer to a service or functionality that is made available by a CSPto users or customers on demand (e.g., via a subscription model) usingsystems and infrastructure (cloud infrastructure) provided by the CSP.Typically, the servers and systems that make up the CSP'sinfrastructure, and which are used to provide a cloud service to acustomer, are separate from the customer's own on-premises servers andsystems. Customers can thus avail themselves of cloud services providedby the CSP without having to purchase separate hardware and softwareresources for the services. Cloud services are designed to provide asubscribing customer easy, scalable, and on-demand access toapplications and computing resources without the customer having toinvest in procuring the infrastructure that is used for providing theservices or functions. Various different types or models of cloudservices may be offered such as Software-as-a-Service (SaaS),Platform-as-a-Service (PaaS), Infrastructure-as-a-Service (IaaS), andothers. A customer can subscribe to one or more cloud services providedby a CSP. The customer can be any entity such as an individual, anorganization, an enterprise, and the like.

As indicated above, a CSP is responsible for providing theinfrastructure and resources that are used for providing cloud servicesto subscribing customers. The resources provided by the CSP can includeboth hardware and software resources. These resources can include, forexample, compute resources (e.g., virtual machines, containers,applications, processors), memory resources (e.g., databases, datastores), networking resources (e.g., routers, host machines, loadbalancers), identity, and other resources. In certain implementations,the resources provided by a CSP for providing a set of cloud servicesCSP are organized into data centers. A data center may be configured toprovide a particular set of cloud services. The CSP is responsible forequipping the data center with infrastructure and resources that areused to provide that particular set of cloud services. A CSP may buildone or more data centers.

Data centers provided by a CSP may be hosted in different regions. Aregion is a localized geographic area and may be identified by a regionname. Regions are generally independent of each other and can beseparated by vast distances, such as across countries or evencontinents. Regions are grouped into realms. Examples of regions for aCSP may include US West, US East, Australia East, Australia Southeast,and the like.

A region can include one or more data centers, where the data centersare located within a certain geographic area corresponding to theregion. As an example, the data centers in a region may be located in acity within that region. For example, for a particular CSP, data centersin the US West region may be located in San Jose, Calif.; data centersin the US East region may be located in Ashburn, Va.; data centers inthe Australia East region may be located in Sydney, Australia; datacenters in the Australia Southeast region may be located in Melbourne,Australia; and the like.

Data centers within a region may be organized into one or moreavailability domains, which are used for high availability and disasterrecovery purposes. An availability domain can include one or more datacenters within a region. Availability domains within a region areisolated from each other, fault tolerant, and are architected in such away that data centers in multiple availability domains are very unlikelyto fail simultaneously. For example, the availability domains within aregion may be structured in a manner such that a failure at oneavailability domain within the region is unlikely to impact theavailability of data centers in other availability domains within thesame region.

When a customer or subscriber subscribes to or signs up for one or moreservices provided by a CSP, the CSP creates a tenancy for the customer.The tenancy is like an account that is created for the customer. Incertain implementations, a tenancy for a customer exists in a singlerealm and can access all regions that belong to that realm. Thecustomer's users can then access the services subscribed to by thecustomer under this tenancy.

As indicated above, a CSP builds or deploys data centers to providecloud services to its customers. As a CSP's customer base grows, the CSPtypically builds new data centers in new regions or increases thecapacity of existing data centers to service the customers' growingdemands and to better serve the customers. Preferably, a data center isbuilt in close geographical proximity to the location of customersserviced by that data center. Geographical proximity between a datacenter and customers serviced by that data center lends to moreefficient use of resources and faster and more reliable services beingprovided to the customers. Accordingly, a CSP typically builds new datacenters in new regions in geographical areas that are geographicallyproximal to the customers serviced by the data centers. For example, fora growing customer base in Germany, a CSP may build one or more datacenters in a new region in Germany.

Building a data center (or multiple data centers) in a region issometimes also referred to as building a region. The term “region build”is used to refer to building one or more data centers in a region.Building a data center in a region involves provisioning or creating aset of new resources that are needed or used for providing a set ofservices that the data center is configured to provide. The end resultof the region build process is the creation of a data center in aregion, where the data center is capable of providing a set of servicesintended for that data center and includes a set of resources that areused to provide the set of services.

Building a new data center in a region is a very complex activityrequiring extensive coordination between various bootstrappingactivities. At a high level, this involves the performance andcoordination of various tasks such as: identifying the set of servicesto be provided by the data center; identifying various resources thatare needed for providing the set of services; creating, provisioning,and deploying the identified resources; wiring the resources properly sothat they can be used in an intended manner; and the like. Each of thesetasks further have subtasks that need to be coordinated, further addingto the complexity. Due to this complexity, presently, the building of adata center in a region involves several manually initiated or manuallycontrolled tasks that require careful manual coordination. As a result,the task of building a new region (i.e., building one or more datacenters in a region) is very time consuming. It can take time, forexample many months, to build a data center. Additionally, the processis very error prone, sometimes requiring several iterations before adesired configuration of the data center is achieved, which further addsto the time taken to build a data center. These limitations and problemsseverely limit a CSP's ability to grow computing resources in a timelymanner responsive to increasing customer needs.

The present disclosure describes techniques for reducing build time,reducing computing resource waste, and reducing risk related to buildingone or more data centers in a region. Instead of weeks and months neededto build a data center in a region in the past, the techniques describedherein can be used to build a new data center in a region in arelatively much shorter time, while reducing the risk of errors overconventional approaches.

A Cloud Infrastructure Orchestration Service (CIOS) is disclosed hereinthat is configured to bootstrap (e.g., provision and deploy) servicesinto a new data center based on predefined configuration files thatidentify the resources (e.g., infrastructure components and software tobe deployed) for implementing a given change to the data center. TheCIOS can parse and analyze configuration files (e.g., flock configs) toidentify dependencies between resources, execution targets, phases, andflocks. The CIOS may generate specific data structures from the analysisand may use these data structures to drive operations and to manage anorder by which services are bootstrapped to a region. The CIOS mayutilize these data structures to identify when it can bootstrap aservice, when bootstrapping is blocked, and/or when bootstrappingoperations associated with a previously blocked service can resume.Advantageously, the CIOS can identify circular dependencies within thedata structures and execute operations to eliminate/resolve thesecircular dependencies prior to task execution. Using these techniques,the CIOS substantially reduces the risk of executing tasks prior to theavailability of the resources on which those tasks depend.

Utilizing the techniques disclosed herein, the CIOS may optimizeparallel processing to execute changes to a data center while ensuringthat tasks are not initiated until the functionality on which thosetasks depend is available in the region. In this manner, the CIOSenables a region build to be performed more efficiently, which greatlyreduces the time required to build a data center and the wastefulcomputing resource use found in conventional approaches.

A Multi-Flock Orchestrator (MFO) (e.g., an orchestration service) isdisclosed herein. MFO may be configured to utilize a number of versionsets that identify differing sets of configuration files to be utilizedfor testing and/or region build. Performing a region build may includeexecuting any suitable operations for provisioning and/or deploying anysuitable number of resources within one or more data centerscorresponding to a region. A particular version set can be used forbuilding the data center(s). That version set can identify a particularset of configuration files from which bootstrapping tasks (e.g.,provisioning and deployment tasks) for the data center may bedetermined. MFO may perform a static analysis of the configuration filesto identify dependencies between services and to identify and resolvecircular dependencies prior to region build. MFO may incrementallyinstruct a provisioning and deployment manager to perform bootstrappingtasks, while ensuring that dependent bootstrapping tasks are notinitiated until the resource on which those tasks depend is available.As various capabilities in the center(s) become available, MFO mayidentify and implement subsequent bootstrapping tasks to be performed,incrementally driving the build process to completion. The disclosedtechniques allow for unit and/or integration tests to be performed withconfiguration files prior to those files being utilized for a regionbuild, which increases the likelihood of a successful region build.Using the disclosed techniques, MFO enables an automated region build tobe performed while reducing the risk of error and time required inconventional systems.

Certain Definitions

A “region” is a logical abstraction corresponding to a geographicallocation. A region can include any suitable number of one or moreexecution targets. In some embodiments, an execution target couldcorrespond to a data center.

An “execution target” refers to a smallest unit of change for executinga release. A “release” refers to a representation of an intent toorchestrate a specific change to a service (e.g., deploy version 8, “addan internal DNS record,” etc.). For most services, an execution targetrepresents an “instance” of a service. A single service can bebootstrapped to each of one or more execution targets. An executiontarget may be associated with a set of devices (e.g., a data center).

“Bootstrapping” is intended to refer to the collective tasks associatedwith provisioning and deployment of any suitable number of resources(e.g., infrastructure components, artifacts, etc.) corresponding to asingle service.

A “service” refers to functionality provided by a set of resources. Aset of resources for a service includes any suitable combination ofinfrastructure, platform, or software (e.g., an application) hosted by acloud provider that can be configured to provide the functionality of aservice. A service can be made available to users through the Internet.

An “artifact” refers to code being deployed to an infrastructurecomponent or a Kubernetes engine cluster, this may include software(e.g., an application), configuration information (e.g., a configurationfile) for an infrastructure component, or the like.

A “flock config” refers to a configuration file (or a set ofconfiguration files) that describes a set of all resources (e.g.,infrastructure components and artifacts) associated with a singleservice. A flock config may include declarative statements that specifyone or more aspects corresponding to a desired state of the resources ofthe service.

“Service state” refers to a point-in-time snapshot of every resource(e.g., infrastructure resources, artifacts, etc.) associated with theservice. The service state indicates status corresponding toprovisioning and/or deployment tasks associated with service resources.

IaaS provisioning (or “provisioning”) refers to acquiring computers orvirtual hosts for use, and even installing needed libraries or serviceson them. The phrase “provisioning a device” refers to evolving a deviceto a state in which it can be utilized by an end-user for their specificuse. A device that has undergone the provisioning process may bereferred to as a “provisioned device.” Preparing the provisioned device(installing libraries and daemons) may be part of provisioning; thispreparation is different from deploying new applications or new versionsof an application onto the prepared device. In most cases, deploymentdoes not include provisioning, and the provisioning may need to beperformed first. Once prepared, the device may be referred to as “aninfrastructure component.”

IaaS deployment (or “deployment”) refers to the process of providingand/or installing a new application, or a new version of an application,onto a provisioned infrastructure component. Once the infrastructurecomponent has been provisioned (e.g., acquired, assigned, prepared,etc.), additional software may be deployed (e.g., provided to andinstalled on the infrastructure component). The infrastructure componentcan be referred to as a “resource” after provisioning and deployment hasconcluded. Examples of resources may include, but are not limited to,virtual machines, databases, object storage, block storage, loadbalancers, and the like.

A “capability” identifies a unit of functionality associated with aservice. The unit could be a portion, or all, of the functionality to beprovided by the service. By way of example, a capability can bepublished indicating that a resource is available forauthorization/authentication processing (e.g., a subset of thefunctionality to be provided by the resource). As another example, acapability can be published indicating the full functionality of theservice is available. Capabilities can be used to identify functionalityon which a resource or service depends and/or functionality of aresource or service that is available for use.

A “virtual bootstrap environment” (ViBE) refers to a virtual cloudnetwork that is provisioned in the overlay of an existing region (e.g.,a “host region”). Once provisioned, a ViBE is connected to a new regionusing a communication channel (e.g., an IPsec Tunnel VPN). Certainessential core services (or “seed” services) like a deploymentorchestrator, a public key infrastructure (PKI) service, and the likecan be provisioned in a ViBE. These services can provide thecapabilities required to bring the hardware online, establish a chain oftrust to the new region, and deploy the remaining services in the newregion. Utilizing the virtual bootstrap environment can prevent circulardependencies between bootstrapping resources by utilizing resources ofthe host region. Services can be staged and tested in the ViBE prior tothe physical region (e.g., the target region) being available.

A “Cloud Infrastructure Orchestration Service” (CIOS) may refer to asystem configured to manage provisioning and deployment operations forany suitable number of services as part of a region build.

A Multi-Flock Orchestrator (MFO) may be a computing component (e.g., aservice) that coordinates events between components of the CIOS toprovision and deploy services to a target region (e.g., a new region).An MFO tracks relevant events for each service of the region build andtakes actions in response to those events.

A “host region” refers to a region that hosts a virtual bootstrapenvironment (ViBE). A host region may be used to bootstrap a ViBE.

A “target region” refers to a region under build.

“Publishing a capability” refers to “publishing” as used in a“publisher-subscriber” computing design or otherwise providing anindication that a particular capability is available (or unavailable).The capabilities are “published” (e.g., collected by a capabilitiesservice, provided to a capabilities service, pushed, pulled, etc.) toprovide an indication that functionality of a resource/service isavailable. In some embodiments, capabilities may bepublished/transmitted via an event, a notification, a data transmission,a function call, an API call, or the like. An event (or othernotification/data transmission/etc.) indicating availability of aparticular capability can be broadcasted/addressed (e.g., published) toa capabilities service.

A “Capabilities Service” may be a flock configured to model dependenciesbetween different flocks. A capabilities service may be provided withina Cloud Infrastructure Orchestration Service and may define whatcapabilities, services, features have been made available in a region.

A “Real-time Regional Data Distributor” (RRDD) may be a service orsystem configured to manage region data. This region data can beinjected into flock configs to dynamically create execution targets fornew regions.

In some examples, techniques for implementing a Cloud InfrastructureOrchestration Service (CIOS) are described herein. Such techniques, asdescribed briefly above, can be configured to manage bootstrapping(e.g., provisioning and deploying software to) infrastructure componentswithin a cloud environment (e.g., a region). In some instances, the CIOScan include computing components (e.g., a CIOS Central and a CIOSRegional, both of which will be described in further detail below) thatmay be configured to manage bootstrapping tasks (provisioning anddeployment) for a given service and a Multi-Flock Orchestrator (alsodescribed in further detail below) configured to initiate/manage regionbuilds (e.g., bootstrapping operations corresponding to multipleservices).

The CIOS enables region building and world-wide infrastructureprovisioning and code deployment with minimal manual run-time effortfrom service teams (e.g., beyond an initial approval and/or physicaltransportation of hardware, in some instances). The high-levelresponsibilities of the CIOS include, but are not limited to,coordinating region builds, providing users with a view of the currentstate of resources managed by the CIOS (e.g., of a region, acrossregions, world-wide, etc.), and managing bootstrapping operations forbootstrapping resources within a region.

The CIOS may provide view reconciliation, where a view of a desiredstate (e.g., a desired configuration) of resources may be reconciledwith a current/actual state (e.g., a current configuration) of theresources. In some instances, view reconciliation may include obtainingstate data to identify what resources are actually running and theircurrent configuration and/or state. Reconciliation can be performed at avariety of granularities, such as at a service level.

The CIOS can perform plan generation, where differences between thedesired and current state of the resources are identified. Part of plangeneration can include identifying the operations that would need to beexecuted to bring the resources from the current state to the desiredstate. In some examples, the CIOS may present a generated plan to a userfor approval. In these examples, the CIOS can mark the plan as approvedor rejected based on user input from the user. Thus, users can spendless time reasoning about the plan and the plans are more accuratebecause they are machine generated. Plans are almost too detailed forhuman consumption; however, the CIOS can provide this data via asophisticated user interface (UI).

In some examples, the CIOS can handle execution of change management byexecuting the approved plan. Once an execution plan has been created andapproved, engineers may no longer need to participate in changemanagement unless the CIOS initiates roll-back. The CIOS can handlerolling back to a previous service version by generating a plan thatreturns the service to a previous (e.g., pre-release) state (e.g., whenCIOS detects service health degradation while executing).

The CIOS can measure service health by monitoring alarms and executingintegration tests. The CIOS can help teams quickly define roll-backbehavior in the event of service degradation, which it can laterexecute. The CIOS can generate and display plans and can track approval.The CIOS can combine the functionality of provisioning and deployment ina single system that coordinates these tasks across a region build. TheCIOS also supports the discovery of flocks (e.g., service resources suchas flock config(s) corresponding to any suitable number of services),artifacts, resources, and dependencies. The CIOS can discoverdependencies between execution tasks at every level (e.g., resourcelevel, execution target level, phase level, service level, etc.) througha static analysis (e.g., including parsing and processing content) ofone or more configuration files. Using these dependencies, the CIOS cangenerate various data structures from these dependencies that can beused to drive task execution (e.g., tasks regarding provisioning ofinfrastructure resources and deployment of artifacts across the region).

FIG. 1 is a block diagram of an environment 100 in which a CloudInfrastructure Orchestration Service (CIOS) 102 may operate todynamically provide bootstrap services in a region, according to atleast one embodiment. CIOS 102 can include, but is not limited to, thefollowing components: Real-time Regional Data Distributor (RRDD) 104,Multi-Flock Orchestrator (WO) 106, CIOS Central 108, CIOS Regional 110,and Capabilities Service 112. Specific functionality of CIOS Central 108and CIOS Regional 110 is provided in more detail in U.S. applicationSer. No. 17/016,754, entitled “Techniques for Deploying InfrastructureResources with a Declarative Provisioning Tool,” the entire contents ofwhich are incorporated in its entirety for all purposes. In someembodiments, any suitable combination of the components of CIOS 102 maybe provided as a service. In some embodiments, some portion of CIOS 102may be deployed to a region (e.g., a data center represented by hostregion 103). In some embodiments, CIOS 102 may include any suitablenumber of cloud services (not depicted in FIG. 1 ) discussed in furtherdetail in U.S. application Ser. No. 17/016,754 and below with respect toFIGS. 2 and 3 .

Real-time Regional Data Distributor (RRDD) 104 may be configured tomaintain and provide region data that identifies realms, regions,execution targets, and availability domains. In some cases, the regiondata may be in any suitable form (e.g., JSON format, dataobjects/containers, XML, etc.). Region data maintained by RRDD 104 mayinclude any suitable number of subsets of data which can individually bereferenceable by a corresponding identifier. By way of example, anidentifier “all regions” can be associated with a data structure (e.g.,a list, a structure, an object, etc.) that includes a metadata for alldefined regions. As another example, an identifier such as “realms” canbe associated with a data structure that identifies metadata for anumber of realms and a set of regions corresponding to each realm. Ingeneral, the region data may maintain any suitable attribute of one ormore realm(s), region(s), availability domains (ADs), executiontarget(s) (ETs), and the like, such as identifiers, DNS suffixes, states(e.g., a state of a region), and the like. The RRDD 104 may beconfigured to manage region state as part of the region data. A regionstate may include any suitable information indicating a state ofbootstrapping within a region. By way of example, some example regionstates can include “initial,” “building,” “production,” “paused,” or“deprecated.” The “initial” state may indicate a region that has not yetbeen bootstrapped. A “building” state may indicate that bootstrapping ofone or more flocks within the region has commenced. A “production” statemay indicate that bootstrapping has been completed and the region isready for validation. A “paused” state may indicate that CIOS Central108 or CIOS Regional 110 has paused internal interactions with theregional stack, likely due to an operational issue. A “deprecated” statemay indicate the region has been deprecated and is likely unavailableand/or will not be contacted again.

CIOS Central 108 is configured to provide any suitable number of userinterfaces with which users (e.g., user 109) may interact with CIOS 102.By way of example, users can make changes to region data via a userinterface provided by CIOS Central 108. CIOS Central 108 mayadditionally provide a variety of interfaces that enable users to: viewchanges made to flock configs and/or artifacts, generate and view plans,approve/reject plans, view status on plan execution (e.g., correspondingto tasks involving infrastructure provisioning, deployment, regionbuild, and/or desired state of any suitable number of resources managedby CIOS 102. CIOS Central 108 may implement a control plane configuredto manage any suitable number of CIOS Regional 110 instances. CIOSCentral 108 can provide one or more user interfaces for presentingregion data, enabling the user 109 to view and/or change region data.CIOS Central 108 can be configured to invoke the functionality of RRDD104 via any suitable number of interfaces. Generally, CIOS Central 108may be configured to manage region data, either directly or indirectly(e.g., via RRDD 104). CIOS Central 108 may be configured to compileflock configs to inject region data as variables within the flockconfigs.

Each instance of CIOS Regional 110 may correspond to a module configuredto execute bootstrapping tasks that are associated with a single serviceof a region. CIOS Regional 110 can receive desired state data from CIOSCentral 108. In some embodiments, desired state data may include a flockconfig that declares (e.g., via declarative statements) a desired stateof resources associated with a service. CIOS Central 108 can maintaincurrent state data indicating any suitable aspect of the current stateof the resources associated with a service. In some embodiments, CIOSRegional 110 can identify, through a comparison of the desired statedata and the current state data, that changes are needed to one or moreresources. For example, CIOS Regional 110 can determine that one or moreinfrastructure components need to be provisioned, one or more artifactsdeployed, or any suitable change needed to the resources of the serviceto bring the state of those resources in line with the desired state. AsCIOS Regional 110 performs bootstrapping operations, it may publish dataindicating various capabilities of a resource as they become available.A “capability” identifies a unit of functionality associated with aservice. The unit could be a portion, or all of the functionality to beprovided by the service. By way of example, a capability can bepublished indicating that a resource is available forauthorization/authentication processing (e.g., a subset of thefunctionality to be provided by the resource). As another example, acapability can be published indicating the full functionality of theservice is available. Capabilities can be used to identify functionalityon which a resource or service depends and/or functionality of aresource or service that is available for use.

Capabilities Service 112 is configured to maintain capabilities datathat indicates 1) what capabilities of various services are currentlyavailable, 2) whether any resource/service is waiting on a particularcapability, 3) what particular resources and/or services are waiting ona given capability, or any suitable combination of the above.Capabilities Service 112 may provide an interface with whichcapabilities data may be requested. Capabilities Service 112 may provideone or more interfaces (e.g., application programming interfaces) thatenable it to transmit capabilities data to MFO 106 and/or CIOS Regional110 (e.g., each instance of CIOS Regional 110). In some embodiments, MFO106 and/or any suitable component or module of CIOS Regional 110 may beconfigured to request capabilities data from Capabilities Service 112.

In some embodiments, Multi-Flock Orchestrator (MFO) 106 may beconfigured to drive region build efforts. In some embodiments, WO 106can manage information that describes what flock/flock config versionsand/or artifact versions are to be utilized to bootstrap a given servicewithin a region (or to make a unit of change to a target region). Insome embodiments, MFO 106 may be configured to monitor (or be otherwisenotified of) changes to the region data managed by Real-time RegionalData Distributor 104. In some embodiments, receiving an indication thatregion data has been changed may cause a region build to be triggered byMFO 106. In some embodiments, WO 106 may collect various flock configsand artifacts to be used for a region build. Some, or all, of the flockconfigs may be configured to be region agnostic. That is, the flockconfigs may not explicitly identify what regions to which the flock isto be bootstrapped. In some embodiments, MFO 106 may trigger a datainjection process through which the collected flock configs arerecompiled (e.g., by CIOS Central 108). During recompilation, operationsmay be executed (e.g., by CIOS Central 108) to cause the region datamaintained by Real-time Regional Data Distributor 104 to be injectedinto the config files. Flock configs can reference region data throughvariables/parameters without requiring hard-coded identification ofregion data. The flock configs can be dynamically modified at run timeusing this data injection rather than having the region data behardcoded, and therefore, and more difficult to change.

Multi-Flock Orchestrator 106 can perform a static flock analysis inwhich the flock configs are parsed to identify dependencies betweenresources, execution targets, phases, and flocks, and in particular toidentify circular dependencies that need to be removed. In someembodiments, MFO 106 can generate any suitable number of data structuresbased on the dependencies identified. These data structures (e.g.,directed acyclic graph(s), linked lists, etc.) may be utilized by theCloud Infrastructure Orchestration Service 102 to drive operations forperforming a region build. By way of example, these data structures maycollectively define an order by which services are bootstrapped within aregion. An example of such a data structure is discussed further belowwith respect to Build Dependency Graph 338 of FIG. 3 . If circulardependencies (e.g., service A requires service B and vice versa) existand are identified through the static flock analysis and/or graph, WOmay be configured to notify any suitable service teams that changes arerequired to the corresponding flock config to correct these circulardependencies. MFO 106 can be configured to traverse one or more datastructures to manage an order by which services are bootstrapped to aregion. MFO 106 can identify (e.g., using data obtained fromCapabilities Service 112) capabilities available within a given regionat any given time. MFO 106 can this data to identify when it canbootstrap a service, when bootstrapping is blocked, and/or whenbootstrapping operations associated with a previously blocked servicecan resume. Based on this traversal, MFO 106 can perform a variety ofreleases in which instructions are transmitted by WO 106 to CIOS Central108 to perform bootstrapping operations corresponding to any suitablenumber of flock configs. In some examples, MFO 106 may be configured toidentify that one or more flock configs may require multiple releasesdue to circular dependencies found within the graph. As a result, MFO106 may transmit multiple instruction sets to CIOS Central 108 for agiven flock config to break the circular dependencies identified in thegraph.

In some embodiments, a user can request that a new region (e.g., targetregion 114) be built. This can involve bootstrapping resourcescorresponding to a variety of services. In some embodiments, targetregion 114 may not be communicatively available (and/or secure) at atime at which the region build request is initiated. Rather than delaybootstrapping until such time as target region 114 is available andconfigured to perform bootstrapping operations, CIOS 102 may initiatethe region build using a virtual bootstrap environment 116. Virtualbootstrap environment (ViBE) 116 may be an overlay network that ishosted by host region 103 (a preexisting region that has previously beenconfigured with a core set of services and which is communicativelyavailable and secure). WO 106 can leverage resources of the host region103 to bootstrap resources to the ViBE 116 (generally referred to as“building the ViBE”). By way of example, MFO 106 can provideinstructions through CIOS Central 108 that cause an instance of CIOSRegional 110 within a host region (e.g., host region 103) to bootstrapanother instance of CIOS Regional within the ViBE 116. Once the CIOSRegional within the ViBE is available for processing, bootstrapping theservices for the target region 114 can continue within the ViBE 116.When target region 114 is available to perform bootstrapping operations,the previously bootstrapped services within ViBE 116 may be migrated totarget region 114. Utilizing these techniques, CIOS 102 can greatlyimprove the speed at which a region is built by drastically reducing theneed for any manual input and/or configuration to be provided.

FIG. 2 is a block diagram for illustrating an environment 200 and methodfor building a virtual bootstrap environment (ViBE) 202 (an example ofViBE 116 of FIG. 1 ), according to at least one embodiment. ViBE 202represents a virtual cloud network that is provisioned in the overlay ofan existing region (e.g., host region 204, an example of the host region103 of FIG. 1 and in an embodiment is a Host Region Service Enclave).ViBE 202 represents an environment in which services can be staged for atarget region (e.g., a region under build such as target region 114 ofFIG. 1 ) before the target region becomes available.

In order to bootstrap a new region (e.g., target region 114 of FIG. 1 ),a core set of services may be bootstrapped. While those core set ofservices exist in the host region 204, they do not yet exist in the ViBE(nor the target region). These essential core services provide thefunctionality needed to provision devices, establish a chain of trust tothe new region, and deploy remaining services (e.g., flocks) into aregion. The ViBE 202 may be a tenancy that is deployed in a host region204. It can be thought of as a virtual region.

When the target region is available to provide bootstrapping operations,the ViBE 202 can be connected to the target region so that services inthe ViBE can interact with the services and/or infrastructure componentsof the target region. This will enable deployment of production levelservices, instead of self-contained seed services as in previoussystems, and will require connectivity over the internet to the targetregion. Conventionally, a seed service was deployed as part of acontainer collection and used to bootstrap dependencies necessary tobuild out the region. Using infrastructure/tooling of an existingregion, resources may be bootstrapped (e.g., provisioned and deployed)into the ViBE 202 and connected to the service enclave of a region(e.g., host region 204) in order to provision hardware and deployservices until the target region is self-sufficient and can becommunicated with directly. Utilizing the ViBE 202 allows for standingup the dependencies and services needed to be able to provision/prepareinfrastructure and deploy software while making use of the host region'sresources in order to break circular dependencies of core services.

Multi-Flock Orchestrator (MFO) 206 may be configured to performoperations to build (e.g., configure) ViBE 202. MFO 206 can obtainapplicable flock configs corresponding to various resources to bebootstrapped to the new region (in this case, a ViBE region, ViBE 202).By way of example, MFO 206 may obtain a flock config (e.g., a “ViBEflock config”) that identifies aspects of bootstrapping CapabilitiesService 208 and Worker 210. As another example, MFO 206 may obtainanother flock config corresponding to bootstrapping Domain Name Service(DNS) 212 to ViBE 202.

At step 1, MFO 206 may instruct CIOS Central 214 (e.g., an example ofCIOS Central 108 and CIOS Central 214 of FIGS. 1 and 2 , respectively).For example, MFO 206 may transmit a request (e.g., including the ViBEflock config) to request bootstrapping of the Capabilities Service 208and Worker 210 that, at this time do not yet exist in the ViBE 202. Insome embodiments, CIOS Central 214 may have access to all flock configs.Therefore, in some examples, MFO 206 may transmit an identifier for theViBE flock config rather than the file itself, and CIOS Central 214 mayindependently obtain it from storage (e.g., from DB 308 or flock DB 312of FIG. 3 ).

At step 2, CIOS Central 214 may provide the ViBE flock config via acorresponding request to CIOS Regional 216. CIOS Regional 216 may parsethe ViBE flock config to identify and execute specific infrastructureprovisioning and deployment operations at step 3.

In some embodiments, the CIOS Regional 216 may utilize additionalcorresponding services for provisioning and deployment. For example, atstep 4, CIOS Regional 216 CIOS Regional may instruct deploymentorchestrator 218 (e.g., an example of a core service, or other write,build, and deploy applications software, of the host region 204) toexecute instructions that in turn cause Capabilities Service 208 andWorker 210 to be bootstrapped within ViBE 202.

At step 5, a capability may be transmitted to the Capabilities Service208 (from the CIOS Regional 216, Deployment Orchestrator 218 via theWorker 210 or otherwise) indicating that resources corresponding to theViBE flock are available. Capabilities Service 208 may persist thisdata. In some embodiments, the Capabilities Service 208 adds thisinformation to a list it maintains of available capabilities with theViBE. By way of example, the capability provided to Capabilities Service208 at step 5 may indicate the Capabilities Service 208 and Worker 210are available for processing.

At step 6, MFO 206 may identify that the capability indicating thatCapabilities Service 208 and Worker 210 are available based on receivingor obtaining data (an identifier corresponding to the capability) fromthe Capabilities Service 208.

At step 7, as a result of receiving/obtaining the data at step 6, theMFO 206 may instruct CIOS Central 214 to bootstrap a DNS service (e.g.,DNS 212) to the ViBE 202. The instructions may identify or include aparticular flock config corresponding to the DNS service.

At step 8, the CIOS Central 214 may instruct the CIOS Regional 216 todeploy DNS 212 to the ViBE 202. In some embodiments, the DNS flockconfig for the DNS 212 is provided by the CIOS Central 214.

At step 9, Worker 210, now that it is deployed in the ViBE 202, may beassigned by CIOS Regional 216 to the task of deploying DNS 212. Workermay execute a declarative infrastructure provisioner in the mannerdescribed above in connection with FIG. 3 to identify (e.g., fromcomparing the flock config (the desired state) to a current state of the(currently non-existing) resources associated with the flock) a set ofoperations that need to be executed to deploy DNS 212.

At step 10, the Deployment Orchestrator 218 may instruct Worker 210 todeploy DNS 212 in accordance with the operations identified at step 9.As depicted, Worker 210 proceeds with executing operations to deploy DNS212 to ViBE 202 at step 11. At step 12, Worker 210 notifies CapabilitiesService 208 that DNS 212 is available in ViBE 202. MFO 206 maysubsequently identify that the resources associated with the ViBE flockconfig and the DNS flock config are available any may proceed tobootstrap any suitable number of additional resources to the ViBE.

After steps 1-12 are concluded, the process for building the ViBE 202can be considered complete and the ViBE 202 can be considered built.

FIG. 3 is a block diagram for illustrating an environment 300 and methodfor bootstrapping services to a target region utilizing the ViBE,according to at least one embodiment.

At step 1, user 302 may utilize any suitable user interface provided byCIOS Central 304 (an example of CIOS Central 108 and CIOS Central 214 ofFIGS. 1 and 2 , respectively) to modify region data. By way of example,user 302 may create a new region to which a number of services are to bebootstrapped.

At step 2, CIOS Central 304 may execute operations to send the change toRRDD 306 (e.g., an example of RRDD 104 of FIG. 1 ). At step 3, RRDD 306may store the received region data in database 308, a data storeconfigured to store region data including any suitable identifier,attribute, state, etc. of a region, AD, realm, ET, or the like. In someembodiments, updater 307 may be utilized to store region data indatabase 308 or any suitable data store from which such updates may beaccessible (e.g., to service teams). In some embodiments, updater 307may be configured to notify (e.g., via any suitable electronicnotification) of updates made to database 308.

At step 4, MFO 310 (an example of the MFO 106 and 206 of FIGS. 1 and 2 ,respectively) may detect the change in region data. In some embodiments,MFO 310 may be configured to poll RRDD 306 for changes in region data.In some embodiments, RRDD 306 may be configured to publish or otherwisenotify MFO 310 of region changes.

At step 5, detecting the change in region data may trigger MFO 310 toobtain a version set (e.g., a version set associated with a particularidentifier such as a “golden version set” identifier). identifying aparticular version for each flock (e.g., service) that is to bebootstrapped to the new region and a particular version for eachartifact corresponding to that flock. The version set may be obtainedfrom DB 312. As flocks evolve and change, the versions for theircorresponding configs and artifacts used for region build may change.These changes may be persisted in flock DB 312 such that MFO 310 mayidentify which versions of flock configs and artifacts to use forbuilding a region (e.g., a ViBE region, a Target Region/non-ViBE Region,etc.). The flock configs (e.g., all versions of the flock configs)and/or artifacts (e.g., all versions of the artifacts) may be stored inDB 308, DB 312, or any suitable data store accessible to the CIOSCentral 304 and/or MFO 310.

At step 6, MFO 310 may request CIOS Central 304 to recompile of each ofthe flock configs associated with the version set with the currentregion data. In some embodiments, the request may indicate a version foreach flock config and/or artifact corresponding to those flock configs.

At step 7, CIOS Central 304 may obtain current region data from the DB308 (e.g., directly, or via Real-time Regional Data Distributor 306) andretrieve any suitable flock config and artifact in accordance with theversions requested by MFO 310.

At step 8, CIOS Central 304 may recompile the flock configs with theregion data obtained at step 7 to inject the flock configs with currentregion data. CIOS Central 304 may return the compiled flock configs toMFO 310. In some embodiments, CIOS Central 304 may simply indicatecompilation is done, and MFO 310 may access the recompiled flock configsvia RRDD 306.

At step 9, MFO 310 may perform a static analysis of the recompiled flockconfigs. As part of the static analysis, MFO 310 may parse the flockconfigs (e.g., using a library associated with a declarativeinfrastructure provisioner (e.g., Terraform, or the like)) to identifydependencies between flocks. From the analysis and the dependenciesidentified, MFO 310 can generate Build Dependency Graph 338. BuildDependency Graph 338 may be an acyclic directed graph that identifies anorder by which flocks are to be bootstrapped (and/or changes indicatedin flock configs are to be applied) to the new region. Each node in thegraph may correspond to bootstrapping any suitable portion of aparticular flock. The specific bootstrapping order may be identifiedbased at least in part on the dependencies. In some embodiments, thedependencies may be expressed as an attribute of the node and/orindicated via edges of the graph that connect the nodes. MFO 310 maytraverse the graph (e.g., beginning at a starting node) to drive theoperations of the region build.

In some embodiments, MFO 310 may utilize a cycle detection algorithm todetect the presence of a cycle (e.g., service A depends on service B andvice versa). MFO 310 can identify orphaned capabilities dependencies.For example, MFO 310 can identify orphaned nodes of the Build DependencyGraph 338 that do not connect to any other nodes. MFO 310 may identifyfalsely published capabilities (e.g., when a capability was prematurelypublished, and the corresponding functionality is not actually yetavailable). WO 310 can detect from the graph that one or more instancesof publishing the same capability exist. In some embodiments, anysuitable number of these errors may be detected and WO 310 (or anothersuitable component such as CIOS Central 304) may be configured to notifyor otherwise present this information to users (e.g., via an electronicnotification, a user interface, or the like). In some embodiments, MFO310 may be configured to force delete/recreate resources to breakcircular dependencies and may once again provide instructions to CIOSCentral 304 to perform bootstrapping operations for those resourcesand/or corresponding flock configs.

A starting node may correspond to bootstrapping the ViBE flock, a secondnode may correspond to bootstrapping DNS. The steps 10-15 correspond todeploying (via deployment orchestrator 317, an example of the deploymentorchestrator 218 of FIG. 2 ) a ViBE flock to ViBE 316 (e.g., an exampleof ViBE 116 and 202 of FIGS. 1, and 2 , respectively). That is, steps10-15 of FIG. 3 generally correspond to steps 1-6 of FIG. 2 . Oncenotified that capabilities exist corresponding to the ViBE flock beingdeployed (e.g., indicating that Capabilities Service 318 and Worker 320,corresponding to Capabilities Service 208 and Worker 210 of FIG. 2 , areavailable) the MFO 310 recommence traversal of the Build DependencyGraph 338 to identify next operations to be executed.

By way of example, MFO 310 may continue traversing the Build DependencyGraph 338 to identify that a DNS flock is to be deployed. Steps 16-21may be executed to deploy DNS 322 (an example of the DNS 212 of FIG. 2). These operations may generally correspond to steps 7-12 of FIG. 2 .

At step 21, a capability may be stored indicating that DNS 322 isavailable. Upon detecting this capability, MFO 310 may recommencetraversal of the Build Dependency Graph 338. On this traversal, the MFO310 may identify that any suitable portion of an instance of CIOSRegional (e.g., an example of CIOS Regional 314) is to be deployed tothe ViBE 316. In some embodiments, steps 16-21 may be substantiallyrepeated with respect to deploying CIOS Regional (ViBE) 326 (an instanceof CIOS Regional 314, CIOS Regional 110 of FIG. 1 ) and Worker 328 tothe ViBE 316. A capability may be transmitted to the CapabilitiesService 318 that CIOS Regional (ViBE) 326 is available.

Upon detecting the CIOS Regional (ViBE) 326 is available, MFO 310 mayrecommence traversal of the Build Dependency Graph 338. On thistraversal, the MFO 310 may identify that a deployment orchestrator(e.g., Deployment Orchestrator 330, an example of the DeploymentOrchestrator 317) is to be deployed to the ViBE 316. In someembodiments, steps 16-21 may be substantially repeated with respect todeploying Deployment Orchestrator 330. Information that identifies acapability may be transmitted to the Capabilities Service 318,indicating that Deployment Orchestrator 330 is available.

After Deployment Orchestrator 330 is deployed, ViBE 316 may beconsidered available for processing subsequent requests. Upon detectingDeployment Orchestrator 330 is available, MFO 310 may instructsubsequent bootstrapping requests to be routed to ViBE components ratherthan utilizing host region components (components of host region 332).Thus, MFO 310 can continue traversing the Build Dependency Graph 338, ateach node instructing flock deployment to the ViBE 316 via CIOS Central304. CIOS Central 304 may request CIOS Regional (ViBE) 326 to deployresources according to the flock config.

At some point during this process, Target Region 334 may becomeavailable. Indication that the Target Region is available may beidentifiable from region data for the Target Region 334 being providedby the user 302 (e.g., as an update to the region data). Theavailability of Target Region 334 may depend on establishing a networkconnection between the Target Region 334 and external networks (e.g.,the Internet). The network connection may be supported over a publicnetwork (e.g., the Internet), but use software security tools (e.g.,IPsec) to provide one or more encrypted tunnels (e.g., IPsec tunnelssuch as tunnel 336) from the ViBE 316 to Target Region 334. As usedherein, “IPsec” refers to a protocol suite for authenticating andencrypting network traffic over a network that uses Internet Protocol(IP) and can include one or more available implementations of theprotocol suite (e.g., Openswan, Libreswan, strongSwan, etc.). Thenetwork may connect the ViBE 316 to the service enclave of the TargetRegion 334.

Prior to establishing the IPsec tunnels, the initial network connectionto the Target Region 334 may be on a connection (e.g., an out-of-bandVPN tunnel) sufficient to allow bootstrapping of networking servicesuntil an IPsec gateway may be deployed on an asset (e.g., bare-metalasset) in the Target Region 334. To bootstrap the Target Region's 334network resources, Deployment Orchestrator 330 can deploy the IPsecgateway at the asset within Target Region 334. The DeploymentOrchestrator 330 may then deploy VPN hosts at the Target Region 334configured to terminate IPsec tunnels from the ViBE 316. Once services(e.g., Deployment Orchestrator 330, Service A, etc.) in the ViBE 316 canestablish an IPsec connection with the VPN hosts in the Target Region334, bootstrapping operations from the ViBE 316 to the Target Region 334may begin.

In some embodiments, the bootstrapping operations may begin withservices in the ViBE 316 provisioning resources in the Target Region 334to support hosting instances of core services as they are deployed fromthe ViBE 316. For example, a host provisioning service may provisionhypervisors on infrastructure (e.g., bare-metal hosts) in the TargetRegion 334 to allocate computing resources for VMs. When the hostprovisioning service completes allocation of physical resources in theTarget Region 334, the host provisioning service may publish informationindicating a capability that indicates that the physical resources inthe Target Region 334 have been allocated. The capability may bepublished to Capabilities Service 318 via CIOS Regional (ViBE) 326(e.g., by Worker 328).

With the hardware allocation of the Target Region 334 established andposted to capabilities service 318, CIOS Regional (ViBE) 326 canorchestrate the deployment of instances of core services from the ViBE316 to the Target Region 334. This deployment may be similar to theprocesses described above for building the ViBE 316, but usingcomponents of the ViBE (e.g., CIOS Regional (ViBE) 326, Worker 328,Deployment Orchestrator 330) instead of components of the Host Region332 service enclave. The deployment operations may generally correspondto steps 16-21 described above.

As a service is deployed from the ViBE 316 to the Target Region 334, theDNS record associated with that service may correspond to the instanceof the service in the ViBE 316. The DNS record associated with theservice may be updated at a later time to complete deployment of theservice to the Target Region 334. Said another way, the instance of theservice in the ViBE 316 may continue to receive traffic (e.g., requests)to the service until the DNS record is updated. A service may deploypartially into the Target Region 334 and publish information indicatinga capability (e.g., to Capabilities Service 318) that the service ispartially deployed. For example, a service running in the ViBE 316 maybe deployed into the Target Region 334 with a corresponding computeinstance, load balancer, and associated applications and other software,but may need to wait for database data to migrate to the Target Region334 before being completely deployed. The DNS record (e.g., managed byDNS 322) may still be associated with the service in the ViBE 316. Oncedata migration for the service is complete, the DNS record may beupdated to point to the operational service deployed in the TargetRegion 334. The deployed service in the Target Region 334 may thenreceive traffic (e.g., requests) for the service, while the instance ofthe service in the ViBE 316 may no longer receive traffic for theservice.

Static Analysis Techniques for Identifying Build Dependencies

FIG. 4 is a block diagram depicting a region 400 (an example of thetarget region 114) associated with a number of flocks, according to atleast one embodiment. The region 400 may be associated withbootstrapping any suitable number of flocks (e.g., flock 1-7,collectively referred to as “flocks 402”). Each flock may correspond toresources (e.g., infrastructure components and software artifacts) to bebootstrapped within the region 400 for a service instance. In someembodiments, some aspect of bootstrapping the resources of a flock maybe dependent on whether capabilities of other flocks are available. Someflocks may be bootstrapped at the same time (e.g., flocks 3, 4, and 5,potentially because those flocks may have capability dependencies incommon). An order may be determined for bootstrapping each flock withinthe region 400 based on identifying these dependencies. Techniques fordoing so are discussed in further detail with respect to FIGS. 6-9 .

FIG. 5 is a block diagram depicting a relationship between a flock 500(e.g., an example of Flock 1 of FIG. 4 ), a number of phases (e.g.,phase 1 and phase 2, as depicted), and a corresponding number ofexecution targets for each phase, according to at least one embodiment.

Each execution target with FIG. 5 depicts a different location at whichthe resources corresponding to flock 500 is to be bootstrapped. By wayof example, each execution target of FIG. 5 may depict a different datacenter or set of devices at which the resources corresponding to flock500 is to be bootstrapped. For any given region build, a flock'sresources (e.g., resources corresponding to a service) may bebootstrapped to any suitable number of execution targets. In someembodiments, bootstrapping operations for a set of execution targets maybe associated with a “phase” and potentially multiple phases may bedefined. In some embodiments, an order by which bootstrapping operationsare performed among a set of execution targets (e.g., ET-1-ET-7,collectively referred to as “execution targets 502”) may be defined andassociated with a phase (e.g., phase 1), while another set of executiontargets (e.g., ET-8-ET-13, collectively referred to as “executiontargets 504”) may be defined and associated with another phase (e.g.,phase 2). In some embodiments, there may be a designated order by whichphases are to be executed. Therefore, a phase may be dependent onanother phase being completed, an execution target may be dependent onone or more other execution targets being completed, and the like. Insome embodiments, a data structure (e.g., phase data structure 506) maybe generated by CIOS 102 of FIG. 1 to identify a set of phases (e.g.,one or more) with which bootstrapping a given service across multipleexecution targets is to be executed, where each phase is associated withone or more execution targets. Any suitable number of data structuresmay be generated for identifying a set of execution targets (e.g.,execution targets 502) and an order by which bootstrapping the serviceacross those set of execution targets is to be executed.

In some embodiments, CIOS 102 of FIG. 1 may maintain any suitable numberof data structures for maintaining dependencies between flocks, phases,execution targets, and the like. In some embodiments, CIOS 102 maygenerate a build dependency graph such as the one discussed in furtherdetail with respect to FIG. 8 .

FIG. 6 depicts an example set of code segments illustrating a number ofdependencies between services, according to at least one embodiment. Thedependencies of FIG. 6 may be identified from one or more flock configs.By way of example, any suitable number of the dependencies discussed inconnection with FIG. 6 may be identified from the code segments of flockconfig 600.

Code segment 602 illustrates one type of dependency (referred to as a“required capability”). The resource block of code segment 602 requeststhat a given source be read (e.g., “dns_a_record”) and that the resultbe exported under the local name “my dns.” Although not depicted,additional statements within the resource block of code segment 602 maybe provided. Code segment 602 illustrates a situation in which the flockconfig 600 includes a dependency on a required capability. That is, thecode segment 602 provides no fallback plan if the resource“dns_a_record” does not exist. Therefore, the code segment 602, whenstatically analyzed (e.g., parsed and evaluated with a predefined set ofrules), may cause the Multi-Flock Orchestrator (e.g., WO 106, 206, and310 of FIGS. 1-3 ) to identify a dependency on “dns_a_record” (e.g., aresource associated with another flock config, not depicted). Since thisdependency indicates a required capability, MFO may be configured toensure (e.g., using nodes of a build dependency graph) that the resource“dns_a_record” exists before instructing bootstrapping tasks beperformed with flock config 600.

Code segment 604 illustrates another type of dependency (referred to asan “optional capability”). To break circular dependencies (for example,a load balancer service requires functionality of a DNS service and viceversa), at least one of the corresponding flock configs may be generatedand/or modified to enable its application(s) and infrastructure capableof running without the other service. By way of example, a DNS flockconfig (e.g., flock config 600) may be defined and/or modified in such away that its corresponding resources can be bootstrapped without a loadbalancer. If the load balancer does not exist, the DNS may be configuredto forward all traffic to a single host. However, when the load balancerexists, the DNS infrastructure and artifacts are redeployed, enablingthe final production configuration of the DNS service to be achieved.Flock configs that provide alternative bootstrapping options when adependent capability (e.g., one on which the flock config depends) isnot present can be said to include an optional dependency on therelevant resource (e.g., the capability of the other service). Thecapability on which a resource of the flock config 600 depends may bereferred to as an “optional capability.”

By way of example, code segment 604 defines a capability “dns_a_record.”The code segment then requests that a resource “dns_a_record” be readand exported as “my dns.” MFO may identify code segment 604 asindicating an optional dependency based at least in part on identifyingdns_a_record as an optional capability. In some embodiments, MFO may beconfigured to identify dns_a_record as an optional capability based atleast in part on identifying a ternary and/or conditional statement tocreate the resource. By way of example, MFO may be configured toidentify the line 606 as being indicative of an optional dependency onthe capability “dns_a_record” due to the use of a ternary operator(e.g., operator “?”). In this case, because the ‘count’ (or for_each)field depends on the result of the capability data source, the resourceof code segment 604 may be identified as optional. Codes segment 604specifies that if the capability “dns_a_record” is present, the resourceof code segment 604 will be created, else, the resource of code segment604 will not be created.

Code segment 608 illustrates another example dependency. While the codesegment 608 may seem similar to the optional dependency discussed abovein connection with code segment 604, code segment 608 may still beidentified as including a required dependency. Code segment 608illustrates a non-count example. Code segment 608 indicates that theresource “dns_a_record” is going to be created, therefore a requireddependency exists between the code segment 608 and the resource“dns_a_record.” The load balancer capability of code segment 608 may beidentified as an optional dependency since the code segment 608 istolerant to the load balancer service not yet being up by falling backto pointing the DNS to a single host as depicted at line 610.

In some embodiments, conflicting dependencies can be identified from agiven flock config. By way of example, if a flock config includes a codesegment that indicates a required dependency on a given resource (e.g.,a resource associated with another service), as well as statementsidentifying an ability to optionally handle the presence of theresource, the required dependency may take precedence over the optionaldependency. In some embodiments, MFO may ensure that the code segmentcorresponding to a given resource (e.g., phase, execution target, flock,etc.) is fully tolerant to the non-presence of anotherresource/capability in order to identify the depended uponresource/capability as optional.

In some embodiments, MFO may be configured to apply dependencies (e.g.,global dependencies) that are not declared within a flock config. Forexample, there may be certain milestones of importance (e.g., fullconnectivity to the region has been established). In some cases, eachflock config of the system may be assumed to require the correspondingcapability without requiring every flock config to explicitly orimplicitly declare the dependency on that capability.

In some embodiments, a dependency may be implicitly or explicitlyidentified. By way of example, flock config 600 may include a statementsuch as “depends_on=resourceA.name.” Code segment 612 illustrates anexplicit dependency at 614 in which the dependency (e.g., a requireddependency on capability 1234) is explicitly defined using the statement“depends_on.” Any dependency identified, that is not identified throughan explicit statement if the dependency (e.g., using the identifier“depends_on”), may be referred to as an “implicit dependency.”

FIG. 7 depicts another example set of code segments illustrating anumber of statically determinable dependencies, according to at leastone embodiment. A “statically determinable dependency” refers to adependency (e.g., required, optional, implicit, explicit, etc.) that canbe determined from code prior to run-time. Some statically determinabledependencies may be identified after compile time (e.g., after the flockconfigs are compiled as described in connection with steps 6-8 of FIG. 3) and before run time of the region build. For a dependency to bestatically determinable (e.g., identifiable using a static analysis(parsing and analysis) of one or more flock configs prior to run time),the values of a code segment from which the dependency is identified maybe locally known (e.g., known within the scope of the flock config inquestion).

By way of example, code segment 702 may be a code segment from which adependency may be statically determinable based at least in part on allvalues (e.g., “my_capability” for parameter “name”) being locally known.The value for the parameter “name” is locally known within flock config700 due to the value being explicitly hard coded within flock config700. Therefore, dependencies may be statically determinable from thecode segment 702 based at least in part on the values for allvariables/parameters being locally known.

Code segment 704 may declare a local variable “name” at 706 that is setto the value “my_capability.” Since the variable “name” is locallydeclared at 706 (e.g., declared as a local variable having local scopeto the flock config 700) the corresponding values are locally known. Insome embodiments, references to parameters defined within a “local”object (as depicted at 707) may be injected at compilation time with thecorresponding values identified in the local object. Therefore, thereference to “local.name” at 708 may be injected with the value“my_capability” (from 706) at compilation time, making identification ofdependencies from code segment 704 statically determinable.

Code segment 710 may declare a local variable “names” at 712 thatincludes a list of values (e.g., strings, identifiers, etc.),“my_capability 1”, “my_capability2”, and “my_capability3”. Since thevariable “names” is locally declared at 713, the corresponding valuesare locally known (e.g., within the scope of flock config 700). In someembodiments, references to parameters defined within a “local” object(as depicted at 713) may be injected at compilation time with thecorresponding values identified in the local object. Therefore, thereferences to “local.names” at 714 and 716 may be injected with thevalues “my_capability1”, “my_capability2”, and “my_capability3” (from713) at compilation time, making identification of dependencies fromcode segment 710 statically determinable.

FIG. 8 illustrates an example portion of a build dependency graph 800,according to at least one embodiment. The build dependency graph 800 maybe an example of the build dependency graph 338 of FIG. 3 generated byMFO 310.

The build dependency graph 800 may be an acyclic directed graph. In someembodiments, the build dependency graph 800 may include any suitablenumber of nodes (e.g., nodes 802-814). Each node of the build dependencygraph 800 may correspond to a flock config (or a portion of a flockconfig) or a capability. As depicted, the nodes 802-814 correspond tobootstrapping operations of a service (in this example, service 1). Eachof nodes 802-814 may correspond to a “release” of a portion of theservice 1 in which instructions may be sent to bootstrap at least aportion of the resources of service 1. The nodes 802-814 and theircorresponding order may be identified (e.g., by the MFO 310 of FIG. 3 )based at least in part on performing a static analysis of the flockconfigs of various services, including one or more flock configsassociated with service 1 (and the corresponding flock configs fromwhich dependencies on capabilities 1-7 are identified). The builddependency graph 800 depicted in FIG. 8 may be one portion of a muchlarger graph. The nodes 802-814 may, among other things, define an orderby which one or more resources (e.g., infrastructure components,software artifacts, etc.) are to be bootstrapped (e.g., provisioned,deployed, etc.) within the region (e.g., at one or more data centerscorresponding to the region). The nodes 802-814 are intended tocorrespond to a particular phase (also identified within the flockconfig(s) associated with service 1).

Capability nodes 1-7 (Capabilities 1-7 as depicted in FIG. 8 , each anexample of a required capability) may indicate capabilities on whichparticular bootstrapping tasks of service 1 depend. Node 802 may depicta starting node for bootstrapping service 1. In some embodiments, node802 may be dependent on one or more capabilities being available (e.g.,as indicated by capability nodes 1-3). In some embodiments, dependenciesbetween node 802 and capabilities 1-3 indicates that bootstrappingservice 1 cannot commence until capabilities 1-3 are available.

Once MFO identifies that capabilities 1-3 are available (e.g., from dataprovided by the capabilities service 318 of FIG. 3 ), it may traverse tonode 804 where a subset of resources (e.g., infrastructure components)are identified as needing to be provisioned. In some embodiments, node804 may be identified as being dependent on capability 6. Therefore, WOmay wait until it identifies capability 6 is available (e.g., from dataprovided by the capabilities service 318) before transmittinginstructions to CIOS Central 304 of FIG. 3 to bootstrap the resourcescorresponding to node 804.

In some embodiments, WO may traverse to node 806 and 812. Node 812 mayindicate dependencies on capabilities 4 and 5. MFO may awaitnotification that capabilities 4 and 5 are available before proceedingpast node 812.

Meanwhile, MFO may instruct CIOS Central 304 to perform bootstrappingoperations corresponding to node 806. In some embodiments, these tasksmay include deploying a portion (e.g., application 1) of service 1. WOmay then proceed to node 808. In some embodiments, node 808 maycorrespond to tasks including deploying a portion (e.g., application 2)of service 1. Node 808 may indicate a dependency on capability 7. MFOmay await notification that capability is available before proceeding tonode 810.

At node 810, MFO may instruct CIOS Central 304 to perform bootstrappingoperations corresponding to node 810. In some embodiments, node 810 maycorrespond to tasks including deploying a portion (e.g., application 3)of service 1. WO may then proceed to node 814.

Node 814 may depend on operations corresponding to nodes 812 and 810 tobe completed. In some embodiments, node 814 may be associated withpublishing a capability indicating that the bootstrap (e.g., phase 1bootstrap) of service 1 is complete. In some embodiments, if MFOidentifies that the operations corresponding to node 812 and 810 havebeen completed, it may publish a capability to the capabilities service318 that indicates bootstrapping service 1 (within phase 1) iscomplete).

Nodes 802-814 depict an example in which MFO 106 has identified that aparticular flock config (e.g., a flock config corresponding to service1) requires multiple releases due to dependencies found within thegraph. As a result, MFO 106 may execute multiple releases correspondingto the instructions for any suitable combination of nodes 802-814 toCIOS Central 304 for a given flock config to break the circulardependencies identified in the graph.

The build dependency graph 800 may be much larger than depicted in FIG.8 defining any suitable number of bootstrapping tasks corresponding toany suitable number of flocks, across any suitable number of executiontargets, according to any suitable number of phases. Utilizing thestatic analysis techniques disclosed herein to generate the builddependency graph 800, MFO can ensure that the order by whichbootstrapping tasks are performed (e.g., between flocks, acrossexecution targets, according to phases) by traversing the graph, whichin turn enables MFO to enforce any dependencies identified through thestatic analysis discussed herein.

MFO may be configured to identify circular dependencies with builddependency graph 800 (e.g., service A requires service B, and viceversa). If circular exist and are identified through the static flockanalysis and/or graph, WO may be configured to notify any suitableservice teams that changes are required to the corresponding flockconfig to correct these circular dependencies. Although not depicted, anorphaned node that does not connect to any other node and/or capabilityof the build dependency graph 800 may be identified as an orphaned node.MFO 310 may identify falsely published capabilities (e.g., when acapability was prematurely published, and the correspondingfunctionality is not actually yet available). WO 310 can detect from thegraph that one or more instances of publishing the same capabilityexist. In some embodiments, any suitable number of these errors may bedetected and WO 310 (or another suitable component such as CIOS Central304) may be configured to notify or otherwise present this informationto users (e.g., via an electronic notification, a user interface, or thelike). In some embodiments, MFO 310 may be configured to forcedelete/recreate resources to break circular dependencies and may onceagain provide instructions to CIOS Central 304 to perform bootstrappingoperations for those resources and/or corresponding flock configs.

FIG. 9 illustrates an example method 900 for performing bootstrapping anumber of services within a region based at least in part on one or moredependencies identified by executing a static analysis of one or moreflock configuration files, according to at least one embodiment. Themethod 900 may be performed by one or more components of the CloudInfrastructure Orchestration Service 102 of FIG. 1 (e.g., Multi-FlockOrchestrator 106 of FIG. 1 ). A computer-readable storage mediumcomprising computer-readable instructions that, upon execution by one ormore processors of a computing device, cause the computing device toperform the 900 800. The method 900 may performed in any suitable order.It should be appreciated that the method 900 may include a greaternumber or a lesser number of steps than that depicted in FIG. 9 .

The method 900 may begin at 902, where a plurality of configurationfiles corresponding to a plurality of services to be bootstrapped to aregion are obtained. In some embodiments, the plurality of configurationfiles provide data (e.g., resource definitions, capability definitions,phase definitions, execution target definitions, etc.) from whichbootstrapping tasks for bootstrapping the plurality of services withinthe region are identifiable.

At 904, one or more dependencies between respective services of theplurality of services may be identified based at least in part onexecuting operations for parsing the plurality of configuration files.By way of example, a static analysis (e.g., one or more parses andanalysis according to a set of predefined rules) may be executed on theconfiguration files to identify required dependencies and/or optionaldependencies (either of which may be explicitly or implicitly defined)between flocks (e.g., between flocks/flock resources and/or betweenphases and/or execution targets).

At 906, a build dependency graph (e.g., build dependency graph 800 ofFIG. 8 ) may be generated based at least in part on the parsing at 904.In some embodiments, the build dependency graph may maintain the one ormore dependencies identified. The build dependency graph may be a datastructure that identifies the plurality of configuration files and theone or more dependencies and indicates a corresponding order with whichbootstrapping tasks are to be performed.

At 908, a provisioning and deployment manager (e.g., CIOS Central 304 ofFIG. 3 ) may be incrementally instructed (e.g., via multiple releases,sets of corresponding instructions) to execute bootstrapping tasks basedat least in part on traversing the build dependency graph. In someembodiments, the bootstrapping tasks may be executed to cause theplurality of services to be bootstrapped to the region according to theone or more dependencies identified.

Example Cloud Service Infrastructure Architecture

As noted above, infrastructure as a service (IaaS) is one particulartype of cloud computing. IaaS can be configured to provide virtualizedcomputing resources over a public network (e.g., the Internet). In anIaaS model, a cloud computing provider can host the infrastructurecomponents (e.g., servers, storage devices, network nodes (e.g.,hardware), deployment software, platform virtualization (e.g., ahypervisor layer), or the like). In some cases, an IaaS provider mayalso supply a variety of services to accompany those infrastructurecomponents (e.g., billing, monitoring, logging, load balancing andclustering, etc.). Thus, as these services may be policy-driven, IaaSusers may be able to implement policies to drive load balancing tomaintain application availability and performance.

In some instances, IaaS customers may access resources and servicesthrough a wide area network (WAN), such as the Internet, and can use thecloud provider's services to install the remaining elements of anapplication stack. For example, the user can log in to the IaaS platformto create virtual machines (VMs), install operating systems (OSs) oneach VM, deploy middleware such as databases, create storage buckets forworkloads and backups, and even install enterprise software into thatVM. Customers can then use the provider's services to perform variousfunctions, including balancing network traffic, troubleshootingapplication issues, monitoring performance, managing disaster recovery,etc.

In most cases, a cloud computing model will require the participation ofa cloud provider. The cloud provider may, but need not be, a third-partyservice that specializes in providing (e.g., offering, renting, selling)IaaS. An entity might also opt to deploy a private cloud, becoming itsown provider of infrastructure services.

In some examples, IaaS deployment is the process of putting a newapplication, or a new version of an application, onto a preparedapplication server or the like. It may also include the process ofpreparing the server (e.g., installing libraries, daemons, etc.). Thisis often managed by the cloud provider, below the hypervisor layer(e.g., the servers, storage, network hardware, and virtualization).Thus, the customer may be responsible for handling (OS), middleware,and/or application deployment (e.g., on self-service virtual machines(e.g., that can be spun up on demand) or the like.

In some examples, IaaS provisioning may refer to acquiring computers orvirtual hosts for use, and even installing needed libraries or serviceson them. In most cases, deployment does not include provisioning, andthe provisioning may need to be performed first.

In some cases, there are two different challenges for IaaS provisioning.First, there is the initial challenge of provisioning the initial set ofinfrastructure before anything is running. Second, there is thechallenge of evolving the existing infrastructure (e.g., adding newservices, changing services, removing services, etc.) once everythinghas been provisioned. In some cases, these two challenges may beaddressed by enabling the configuration of the infrastructure to bedefined declaratively. In other words, the infrastructure (e.g., whatcomponents are needed and how they interact) can be defined by one ormore configuration files. Thus, the overall topology of theinfrastructure (e.g., what resources depend on which, and how they eachwork together) can be described declaratively. In some instances, oncethe topology is defined, a workflow can be generated that creates and/ormanages the different components described in the configuration files.

In some examples, an infrastructure may have many interconnectedelements. For example, there may be one or more virtual private clouds(VPCs) (e.g., a potentially on-demand pool of configurable and/or sharedcomputing resources), also known as a core network. In some examples,there may also be one or more inbound/outbound traffic group rulesprovisioned to define how the inbound and/or outbound traffic of thenetwork will be set up and one or more virtual machines (VMs). Otherinfrastructure elements may also be provisioned, such as a loadbalancer, a database, or the like. As more and more infrastructureelements are desired and/or added, the infrastructure may incrementallyevolve.

In some instances, continuous deployment techniques may be employed toenable deployment of infrastructure code across various virtualcomputing environments. Additionally, the described techniques canenable infrastructure management within these environments. In someexamples, service teams can write code that is desired to be deployed toone or more, but often many, different production environments (e.g.,across various different geographic locations, sometimes spanning theentire world). However, in some examples, the infrastructure on whichthe code will be deployed must first be set up. In some instances, theprovisioning can be done manually, a provisioning tool may be utilizedto provision the resources, and/or deployment tools may be utilized todeploy the code once the infrastructure is provisioned.

FIG. 10 is a block diagram 1000 illustrating an example pattern of anIaaS architecture, according to at least one embodiment. Serviceoperators 1002 can be communicatively coupled to a secure host tenancy1004 that can include a virtual cloud network (VCN) 1006 and a securehost subnet 1008. In some examples, the service operators 1002 may beusing one or more client computing devices, which may be portablehandheld devices (e.g., an iPhone®, cellular telephone, an iPad®,computing tablet, a personal digital assistant (PDA)) or wearabledevices (e.g., a Google Glass® head mounted display), running softwaresuch as Microsoft Windows Mobile®, and/or a variety of mobile operatingsystems such as iOS, Windows Phone, Android, BlackBerry 8, Palm OS, andthe like, and being Internet, e-mail, short message service (SMS),Blackberry®, or other communication protocol enabled. Alternatively, theclient computing devices can be general purpose personal computersincluding, by way of example, personal computers and/or laptop computersrunning various versions of Microsoft Windows®, Apple Macintosh®, and/orLinux operating systems. The client computing devices can be workstationcomputers running any of a variety of commercially available UNIX® orUNIX-like operating systems, including without limitation the variety ofGNU/Linux operating systems, such as for example, Google Chrome OS.Alternatively, or in addition, client computing devices may be any otherelectronic device, such as a thin-client computer, an Internet-enabledgaming system (e.g., a Microsoft Xbox gaming console with or without aKinect® gesture input device), and/or a personal messaging device,capable of communicating over a network that can access the VCN 1006and/or the Internet.

The VCN 1006 can include a local peering gateway (LPG) 1010 that can becommunicatively coupled to a secure shell (SSH) VCN 1012 via an LPG 1010contained in the SSH VCN 1012. The SSH VCN 1012 can include an SSHsubnet 1014, and the SSH VCN 1012 can be communicatively coupled to acontrol plane VCN 1016 via the LPG 1010 contained in the control planeVCN 1016. Also, the SSH VCN 1012 can be communicatively coupled to adata plane VCN 1018 via an LPG 1010. The control plane VCN 1016 and thedata plane VCN 1018 can be contained in a service tenancy 1019 that canbe owned and/or operated by the IaaS provider.

The control plane VCN 1016 can include a control plane demilitarizedzone (DMZ) tier 1020 that acts as a perimeter network (e.g., portions ofa corporate network between the corporate intranet and externalnetworks). The DMZ-based servers may have restricted responsibilitiesand help keep breaches contained. Additionally, the DMZ tier 1020 caninclude one or more load balancer (LB) subnet(s) 1022, a control planeapp tier 1024 that can include app subnet(s) 1026, a control plane datatier 1028 that can include database (DB) subnet(s) 1030 (e.g., frontendDB subnet(s) and/or backend DB subnet(s)). The LB subnet(s) 1022contained in the control plane DMZ tier 1020 can be communicativelycoupled to the app subnet(s) 1026 contained in the control plane apptier 1024 and an Internet gateway 1034 that can be contained in thecontrol plane VCN 1016, and the app subnet(s) 1026 can becommunicatively coupled to the DB subnet(s) 1030 contained in thecontrol plane data tier 1028 and a service gateway 1036 and a networkaddress translation (NAT) gateway 1038. The control plane VCN 1016 caninclude the service gateway 1036 and the NAT gateway 1038.

The control plane VCN 1016 can include a data plane mirror app tier 1040that can include app subnet(s) 1026. The app subnet(s) 1026 contained inthe data plane mirror app tier 1040 can include a virtual networkinterface controller (VNIC) 1042 that can execute a compute instance1044. The compute instance 1044 can communicatively couple the appsubnet(s) 1026 of the data plane mirror app tier 1040 to app subnet(s)1026 that can be contained in a data plane app tier 1046.

The data plane VCN 1018 can include the data plane app tier 1046, a dataplane DMZ tier 1048, and a data plane data tier 1050. The data plane DMZtier 1048 can include LB subnet(s) 1022 that can be communicativelycoupled to the app subnet(s) 1026 of the data plane app tier 1046 andthe Internet gateway 1034 of the data plane VCN 1018. The app subnet(s)1026 can be communicatively coupled to the service gateway 1036 of thedata plane VCN 1018 and the NAT gateway 1038 of the data plane VCN 1018.The data plane data tier 1050 can also include the DB subnet(s) 1030that can be communicatively coupled to the app subnet(s) 1026 of thedata plane app tier 1046.

The Internet gateway 1034 of the control plane VCN 1016 and of the dataplane VCN 1018 can be communicatively coupled to a metadata managementservice 1052 that can be communicatively coupled to public Internet1054. Public Internet 1054 can be communicatively coupled to the NATgateway 1038 of the control plane VCN 1016 and of the data plane VCN1018. The service gateway 1036 of the control plane VCN 1016 and of thedata plane VCN 1018 can be communicatively couple to cloud services1056.

In some examples, the service gateway 1036 of the control plane VCN 1016or of the data plane VCN 1018 can make application programming interface(API) calls to cloud services 1056 without going through public Internet1054. The API calls to cloud services 1056 from the service gateway 1036can be one-way: the service gateway 1036 can make API calls to cloudservices 1056, and cloud services 1056 can send requested data to theservice gateway 1036. But, cloud services 1056 may not initiate APIcalls to the service gateway 1036.

In some examples, the secure host tenancy 1004 can be directly connectedto the service tenancy 1019, which may be otherwise isolated. The securehost subnet 1008 can communicate with the SSH subnet 1014 through an LPG1010 that may enable two-way communication over an otherwise isolatedsystem. Connecting the secure host subnet 1008 to the SSH subnet 1014may give the secure host subnet 1008 access to other entities within theservice tenancy 1019.

The control plane VCN 1016 may allow users of the service tenancy 1019to set up or otherwise provision desired resources. Desired resourcesprovisioned in the control plane VCN 1016 may be deployed or otherwiseused in the data plane VCN 1018. In some examples, the control plane VCN1016 can be isolated from the data plane VCN 1018, and the data planemirror app tier 1040 of the control plane VCN 1016 can communicate withthe data plane app tier 1046 of the data plane VCN 1018 via VNICs 1042that can be contained in the data plane mirror app tier 1040 and thedata plane app tier 1046.

In some examples, users of the system, or customers, can make requests,for example create, read, update, or delete (CRUD) operations, throughpublic Internet 1054 that can communicate the requests to the metadatamanagement service 1052. The metadata management service 1052 cancommunicate the request to the control plane VCN 1016 through theInternet gateway 1034. The request can be received by the LB subnet(s)1022 contained in the control plane DMZ tier 1020. The LB subnet(s) 1022may determine that the request is valid, and in response to thisdetermination, the LB subnet(s) 1022 can transmit the request to appsubnet(s) 1026 contained in the control plane app tier 1024. If therequest is validated and requires a call to public Internet 1054, thecall to public Internet 1054 may be transmitted to the NAT gateway 1038that can make the call to public Internet 1054. Memory that may bedesired to be stored by the request can be stored in the DB subnet(s)1030.

In some examples, the data plane mirror app tier 1040 can facilitatedirect communication between the control plane VCN 1016 and the dataplane VCN 1018. For example, changes, updates, or other suitablemodifications to configuration may be desired to be applied to theresources contained in the data plane VCN 1018. Via a VNIC 1042, thecontrol plane VCN 1016 can directly communicate with, and can therebyexecute the changes, updates, or other suitable modifications toconfiguration to, resources contained in the data plane VCN 1018.

In some embodiments, the control plane VCN 1016 and the data plane VCN1018 can be contained in the service tenancy 1019. In this case, theuser, or the customer, of the system may not own or operate either thecontrol plane VCN 1016 or the data plane VCN 1018. Instead, the IaaSprovider may own or operate the control plane VCN 1016 and the dataplane VCN 1018, both of which may be contained in the service tenancy1019. This embodiment can enable isolation of networks that may preventusers or customers from interacting with other users', or othercustomers', resources. Also, this embodiment may allow users orcustomers of the system to store databases privately without needing torely on public Internet 1054, which may not have a desired level ofthreat prevention, for storage.

In other embodiments, the LB subnet(s) 1022 contained in the controlplane VCN 1016 can be configured to receive a signal from the servicegateway 1036. In this embodiment, the control plane VCN 1016 and thedata plane VCN 1018 may be configured to be called by a customer of theIaaS provider without calling public Internet 1054. Customers of theIaaS provider may desire this embodiment since database(s) that thecustomers use may be controlled by the IaaS provider and may be storedon the service tenancy 1019, which may be isolated from public Internet1054.

FIG. 11 is a block diagram 1100 illustrating another example pattern ofan IaaS architecture, according to at least one embodiment. Serviceoperators 1102 (e.g., service operators 1002 of FIG. 10 ) can becommunicatively coupled to a secure host tenancy 1104 (e.g., the securehost tenancy 1004 of FIG. 10 ) that can include a virtual cloud network(VCN) 1106 (e.g., the VCN 1006 of FIG. 10 ) and a secure host subnet1108 (e.g., the secure host subnet 1008 of FIG. 10 ). The VCN 1106 caninclude a local peering gateway (LPG) 1110 (e.g., the LPG 1010 of FIG.10 ) that can be communicatively coupled to a secure shell (SSH) VCN1112 (e.g., the SSH VCN 1012 of FIG. 10 ) via an LPG 1010 contained inthe SSH VCN 1112. The SSH VCN 1112 can include an SSH subnet 1114 (e.g.,the SSH subnet 1014 of FIG. 10 ), and the SSH VCN 1112 can becommunicatively coupled to a control plane VCN 1116 (e.g., the controlplane VCN 1016 of FIG. 10 ) via an LPG 1110 contained in the controlplane VCN 1116. The control plane VCN 1116 can be contained in a servicetenancy 1119 (e.g., the service tenancy 1019 of FIG. 10 ), and the dataplane VCN 1118 (e.g., the data plane VCN 1018 of FIG. 10 ) can becontained in a customer tenancy 1121 that may be owned or operated byusers, or customers, of the system.

The control plane VCN 1116 can include a control plane DMZ tier 1120(e.g., the control plane DMZ tier 1020 of FIG. 10 ) that can include LBsubnet(s) 1122 (e.g., LB subnet(s) 1022 of FIG. 10 ), a control planeapp tier 1124 (e.g., the control plane app tier 1024 of FIG. 10 ) thatcan include app subnet(s) 1126 (e.g., app subnet(s) 1026 of FIG. 10 ), acontrol plane data tier 1128 (e.g., the control plane data tier 1028 ofFIG. 10 ) that can include database (DB) subnet(s) 1130 (e.g., similarto DB subnet(s) 1030 of FIG. 10 ). The LB subnet(s) 1122 contained inthe control plane DMZ tier 1120 can be communicatively coupled to theapp subnet(s) 1126 contained in the control plane app tier 1124 and anInternet gateway 1134 (e.g., the Internet gateway 1034 of FIG. 10 ) thatcan be contained in the control plane VCN 1116, and the app subnet(s)1126 can be communicatively coupled to the DB subnet(s) 1130 containedin the control plane data tier 1128 and a service gateway 1136 (e.g.,the service gateway 1036 of FIG. 10 ) and a network address translation(NAT) gateway 1138 (e.g., the NAT gateway 1038 of FIG. 10 ). The controlplane VCN 1116 can include the service gateway 1136 and the NAT gateway1138.

The control plane VCN 1116 can include a data plane mirror app tier 1140(e.g., the data plane mirror app tier 1040 of FIG. 10 ) that can includeapp subnet(s) 1126. The app subnet(s) 1126 contained in the data planemirror app tier 1140 can include a virtual network interface controller(VNIC) 1142 (e.g., the VNIC of 1042) that can execute a compute instance1144 (e.g., similar to the compute instance 1044 of FIG. 10 ). Thecompute instance 1144 can facilitate communication between the appsubnet(s) 1126 of the data plane mirror app tier 1140 and the appsubnet(s) 1126 that can be contained in a data plane app tier 1146(e.g., the data plane app tier 1046 of FIG. 10 ) via the VNIC 1142contained in the data plane mirror app tier 1140 and the VNIC 1142contained in the data plane app tier 1146.

The Internet gateway 1134 contained in the control plane VCN 1116 can becommunicatively coupled to a metadata management service 1152 (e.g., themetadata management service 1052 of FIG. 10 ) that can becommunicatively coupled to public Internet 1154 (e.g., public Internet1054 of FIG. 10 ). Public Internet 1154 can be communicatively coupledto the NAT gateway 1138 contained in the control plane VCN 1116. Theservice gateway 1136 contained in the control plane VCN 1116 can becommunicatively couple to cloud services 1156 (e.g., cloud services 1056of FIG. 10 ).

In some examples, the data plane VCN 1118 can be contained in thecustomer tenancy 1121. In this case, the IaaS provider may provide thecontrol plane VCN 1116 for each customer, and the IaaS provider may, foreach customer, set up a unique compute instance 1144 that is containedin the service tenancy 1119. Each compute instance 1144 may allowcommunication between the control plane VCN 1116, contained in theservice tenancy 1119, and the data plane VCN 1118 that is contained inthe customer tenancy 1121. The compute instance 1144 may allowresources, that are provisioned in the control plane VCN 1116 that iscontained in the service tenancy 1119, to be deployed or otherwise usedin the data plane VCN 1118 that is contained in the customer tenancy1121.

In other examples, the customer of the IaaS provider may have databasesthat live in the customer tenancy 1121. In this example, the controlplane VCN 1116 can include the data plane mirror app tier 1140 that caninclude app subnet(s) 1126. The data plane mirror app tier 1140 canreside in the data plane VCN 1118, but the data plane mirror app tier1140 may not live in the data plane VCN 1118. That is, the data planemirror app tier 1140 may have access to the customer tenancy 1121, butthe data plane mirror app tier 1140 may not exist in the data plane VCN1118 or be owned or operated by the customer of the IaaS provider. Thedata plane mirror app tier 1140 may be configured to make calls to thedata plane VCN 1118 but may not be configured to make calls to anyentity contained in the control plane VCN 1116. The customer may desireto deploy or otherwise use resources in the data plane VCN 1118 that areprovisioned in the control plane VCN 1116, and the data plane mirror apptier 1140 can facilitate the desired deployment, or other usage ofresources, of the customer.

In some embodiments, the customer of the IaaS provider can apply filtersto the data plane VCN 1118. In this embodiment, the customer candetermine what the data plane VCN 1118 can access, and the customer mayrestrict access to public Internet 1154 from the data plane VCN 1118.The IaaS provider may not be able to apply filters or otherwise controlaccess of the data plane VCN 1118 to any outside networks or databases.Applying filters and controls by the customer onto the data plane VCN1118, contained in the customer tenancy 1121, can help isolate the dataplane VCN 1118 from other customers and from public Internet 1154.

In some embodiments, cloud services 1156 can be called by the servicegateway 1136 to access services that may not exist on public Internet1154, on the control plane VCN 1116, or on the data plane VCN 1118. Theconnection between cloud services 1156 and the control plane VCN 1116 orthe data plane VCN 1118 may not be live or continuous. Cloud services1156 may exist on a different network owned or operated by the IaaSprovider. Cloud services 1156 may be configured to receive calls fromthe service gateway 1136 and may be configured to not receive calls frompublic Internet 1154. Some cloud services 1156 may be isolated fromother cloud services 1156, and the control plane VCN 1116 may beisolated from cloud services 1156 that may not be in the same region asthe control plane VCN 1116. For example, the control plane VCN 1116 maybe located in “Region 1,” and cloud service “Deployment 10,” may belocated in Region 1 and in “Region 2.” If a call to Deployment 10 ismade by the service gateway 1136 contained in the control plane VCN 1116located in Region 1, the call may be transmitted to Deployment 10 inRegion 1. In this example, the control plane VCN 1116, or Deployment 10in Region 1, may not be communicatively coupled to, or otherwise incommunication with, Deployment 10 in Region 2.

FIG. 12 is a block diagram 1200 illustrating another example pattern ofan IaaS architecture, according to at least one embodiment. Serviceoperators 1202 (e.g., service operators 1002 of FIG. 10 ) can becommunicatively coupled to a secure host tenancy 1204 (e.g., the securehost tenancy 1004 of FIG. 10 ) that can include a virtual cloud network(VCN) 1206 (e.g., the VCN 1006 of FIG. 10 ) and a secure host subnet1208 (e.g., the secure host subnet 1008 of FIG. 10 ). The VCN 1206 caninclude an LPG 1210 (e.g., the LPG 1010 of FIG. 10 ) that can becommunicatively coupled to an SSH VCN 1212 (e.g., the SSH VCN 1012 ofFIG. 10 ) via an LPG 1210 contained in the SSH VCN 1212. The SSH VCN1212 can include an SSH subnet 1214 (e.g., the SSH subnet 1014 of FIG.10 ), and the SSH VCN 1212 can be communicatively coupled to a controlplane VCN 1216 (e.g., the control plane VCN 1016 of FIG. 10 ) via an LPG1210 contained in the control plane VCN 1216 and to a data plane VCN1218 (e.g., the data plane 1018 of FIG. 10 ) via an LPG 1210 containedin the data plane VCN 1218. The control plane VCN 1216 and the dataplane VCN 1218 can be contained in a service tenancy 1219 (e.g., theservice tenancy 1019 of FIG. 10 ).

The control plane VCN 1216 can include a control plane DMZ tier 1220(e.g., the control plane DMZ tier 1020 of FIG. 10 ) that can includeload balancer (LB) subnet(s) 1222 (e.g., LB subnet(s) 1022 of FIG. 10 ),a control plane app tier 1224 (e.g., the control plane app tier 1024 ofFIG. 10 ) that can include app subnet(s) 1226 (e.g., similar to appsubnet(s) 1026 of FIG. 10 ), a control plane data tier 1228 (e.g., thecontrol plane data tier 1028 of FIG. 10 ) that can include DB subnet(s)1230. The LB subnet(s) 1222 contained in the control plane DMZ tier 1220can be communicatively coupled to the app subnet(s) 1226 contained inthe control plane app tier 1224 and to an Internet gateway 1234 (e.g.,the Internet gateway 1034 of FIG. 10 ) that can be contained in thecontrol plane VCN 1216, and the app subnet(s) 1226 can becommunicatively coupled to the DB subnet(s) 1230 contained in thecontrol plane data tier 1228 and to a service gateway 1236 (e.g., theservice gateway of FIG. 10 ) and a network address translation (NAT)gateway 1238 (e.g., the NAT gateway 1038 of FIG. 10 ). The control planeVCN 1216 can include the service gateway 1236 and the NAT gateway 1238.

The data plane VCN 1218 can include a data plane app tier 1246 (e.g.,the data plane app tier 1046 of FIG. 10 ), a data plane DMZ tier 1248(e.g., the data plane DMZ tier 1048 of FIG. 10 ), and a data plane datatier 1250 (e.g., the data plane data tier 1050 of FIG. 10 ). The dataplane DMZ tier 1248 can include LB subnet(s) 1222 that can becommunicatively coupled to trusted app subnet(s) 1260 and untrusted appsubnet(s) 1262 of the data plane app tier 1246 and the Internet gateway1234 contained in the data plane VCN 1218. The trusted app subnet(s)1260 can be communicatively coupled to the service gateway 1236contained in the data plane VCN 1218, the NAT gateway 1238 contained inthe data plane VCN 1218, and DB subnet(s) 1230 contained in the dataplane data tier 1250. The untrusted app subnet(s) 1262 can becommunicatively coupled to the service gateway 1236 contained in thedata plane VCN 1218 and DB subnet(s) 1230 contained in the data planedata tier 1250. The data plane data tier 1250 can include DB subnet(s)1230 that can be communicatively coupled to the service gateway 1236contained in the data plane VCN 1218.

The untrusted app subnet(s) 1262 can include one or more primary VNICs1264(1)-(N) that can be communicatively coupled to tenant virtualmachines (VMs) 1266(1)-(N). Each tenant VM 1266(1)-(N) can becommunicatively coupled to a respective app subnet 1267(1)-(N) that canbe contained in respective container egress VCNs 1268(1)-(N) that can becontained in respective customer tenancies 1270(1)-(N). Respectivesecondary VNICs 1272(1)-(N) can facilitate communication between theuntrusted app subnet(s) 1262 contained in the data plane VCN 1218 andthe app subnet contained in the container egress VCNs 1268(1)-(N). Eachcontainer egress VCNs 1268(1)-(N) can include a NAT gateway 1238 thatcan be communicatively coupled to public Internet 1254 (e.g., publicInternet 1054 of FIG. 10 ).

The Internet gateway 1234 contained in the control plane VCN 1216 andcontained in the data plane VCN 1218 can be communicatively coupled to ametadata management service 1252 (e.g., the metadata management system1052 of FIG. 10 ) that can be communicatively coupled to public Internet1254. Public Internet 1254 can be communicatively coupled to the NATgateway 1238 contained in the control plane VCN 1216 and contained inthe data plane VCN 1218. The service gateway 1236 contained in thecontrol plane VCN 1216 and contained in the data plane VCN 1218 can becommunicatively couple to cloud services 1256.

In some embodiments, the data plane VCN 1218 can be integrated withcustomer tenancies 1270. This integration can be useful or desirable forcustomers of the IaaS provider in some cases such as a case that maydesire support when executing code. The customer may provide code to runthat may be destructive, may communicate with other customer resources,or may otherwise cause undesirable effects. In response to this, theIaaS provider may determine whether to run code given to the IaaSprovider by the customer.

In some examples, the customer of the IaaS provider may grant temporarynetwork access to the IaaS provider and request a function to beattached to the data plane app tier 1246. Code to run the function maybe executed in the VMs 1266(1)-(N), and the code may not be configuredto run anywhere else on the data plane VCN 1218. Each VM 1266(1)-(N) maybe connected to one customer tenancy 1270. Respective containers1271(1)-(N) contained in the VMs 1266(1)-(N) may be configured to runthe code. In this case, there can be a dual isolation (e.g., thecontainers 1271(1)-(N) running code, where the containers 1271(1)-(N)may be contained in at least the VM 1266(1)-(N) that are contained inthe untrusted app subnet(s) 1262), which may help prevent incorrect orotherwise undesirable code from damaging the network of the IaaSprovider or from damaging a network of a different customer. Thecontainers 1271(1)-(N) may be communicatively coupled to the customertenancy 1270 and may be configured to transmit or receive data from thecustomer tenancy 1270. The containers 1271(1)-(N) may not be configuredto transmit or receive data from any other entity in the data plane VCN1218. Upon completion of running the code, the IaaS provider may kill orotherwise dispose of the containers 1271(1)-(N).

In some embodiments, the trusted app subnet(s) 1260 may run code thatmay be owned or operated by the IaaS provider. In this embodiment, thetrusted app subnet(s) 1260 may be communicatively coupled to the DBsubnet(s) 1230 and be configured to execute CRUD operations in the DBsubnet(s) 1230. The untrusted app subnet(s) 1262 may be communicativelycoupled to the DB subnet(s) 1230, but in this embodiment, the untrustedapp subnet(s) may be configured to execute read operations in the DBsubnet(s) 1230. The containers 1271(1)-(N) that can be contained in theVM 1266(1)-(N) of each customer and that may run code from the customermay not be communicatively coupled with the DB subnet(s) 1230.

In other embodiments, the control plane VCN 1216 and the data plane VCN1218 may not be directly communicatively coupled. In this embodiment,there may be no direct communication between the control plane VCN 1216and the data plane VCN 1218. However, communication can occur indirectlythrough at least one method. An LPG 1210 may be established by the IaaSprovider that can facilitate communication between the control plane VCN1216 and the data plane VCN 1218. In another example, the control planeVCN 1216 or the data plane VCN 1218 can make a call to cloud services1256 via the service gateway 1236. For example, a call to cloud services1256 from the control plane VCN 1216 can include a request for a servicethat can communicate with the data plane VCN 1218.

FIG. 13 is a block diagram 1300 illustrating another example pattern ofan IaaS architecture, according to at least one embodiment. Serviceoperators 1302 (e.g., service operators 1002 of FIG. 10 ) can becommunicatively coupled to a secure host tenancy 1304 (e.g., the securehost tenancy 1004 of FIG. 10 ) that can include a virtual cloud network(VCN) 1306 (e.g., the VCN 1006 of FIG. 10 ) and a secure host subnet1308 (e.g., the secure host subnet 1008 of FIG. 10 ). The VCN 1306 caninclude an LPG 1310 (e.g., the LPG 1010 of FIG. 10 ) that can becommunicatively coupled to an SSH VCN 1312 (e.g., the SSH VCN 1012 ofFIG. 10 ) via an LPG 1310 contained in the SSH VCN 1312. The SSH VCN1312 can include an SSH subnet 1314 (e.g., the SSH subnet 1014 of FIG.10 ), and the SSH VCN 1312 can be communicatively coupled to a controlplane VCN 1316 (e.g., the control plane VCN 1016 of FIG. 10 ) via an LPG1310 contained in the control plane VCN 1316 and to a data plane VCN1318 (e.g., the data plane 1018 of FIG. 10 ) via an LPG 1310 containedin the data plane VCN 1318. The control plane VCN 1316 and the dataplane VCN 1318 can be contained in a service tenancy 1319 (e.g., theservice tenancy 1019 of FIG. 10 ).

The control plane VCN 1316 can include a control plane DMZ tier 1320(e.g., the control plane DMZ tier 1020 of FIG. 10 ) that can include LBsubnet(s) 1322 (e.g., LB subnet(s) 1022 of FIG. 10 ), a control planeapp tier 1324 (e.g., the control plane app tier 1024 of FIG. 10 ) thatcan include app subnet(s) 1326 (e.g., app subnet(s) 1026 of FIG. 10 ), acontrol plane data tier 1328 (e.g., the control plane data tier 1028 ofFIG. 10 ) that can include DB subnet(s) 1330 (e.g., DB subnet(s) 1230 ofFIG. 12 ). The LB subnet(s) 1322 contained in the control plane DMZ tier1320 can be communicatively coupled to the app subnet(s) 1326 containedin the control plane app tier 1324 and to an Internet gateway 1334(e.g., the Internet gateway 1034 of FIG. 10 ) that can be contained inthe control plane VCN 1316, and the app subnet(s) 1326 can becommunicatively coupled to the DB subnet(s) 1330 contained in thecontrol plane data tier 1328 and to a service gateway 1336 (e.g., theservice gateway of FIG. 10 ) and a network address translation (NAT)gateway 1338 (e.g., the NAT gateway 1038 of FIG. 10 ). The control planeVCN 1316 can include the service gateway 1336 and the NAT gateway 1338.

The data plane VCN 1318 can include a data plane app tier 1346 (e.g.,the data plane app tier 1046 of FIG. 10 ), a data plane DMZ tier 1348(e.g., the data plane DMZ tier 1048 of FIG. 10 ), and a data plane datatier 1350 (e.g., the data plane data tier 1050 of FIG. 10 ). The dataplane DMZ tier 1348 can include LB subnet(s) 1322 that can becommunicatively coupled to trusted app subnet(s) 1360 (e.g., trusted appsubnet(s) 1260 of FIG. 12 ) and untrusted app subnet(s) 1362 (e.g.,untrusted app subnet(s) 1262 of FIG. 12 ) of the data plane app tier1346 and the Internet gateway 1334 contained in the data plane VCN 1318.The trusted app subnet(s) 1360 can be communicatively coupled to theservice gateway 1336 contained in the data plane VCN 1318, the NATgateway 1338 contained in the data plane VCN 1318, and DB subnet(s) 1330contained in the data plane data tier 1350. The untrusted app subnet(s)1362 can be communicatively coupled to the service gateway 1336contained in the data plane VCN 1318 and DB subnet(s) 1330 contained inthe data plane data tier 1350. The data plane data tier 1350 can includeDB subnet(s) 1330 that can be communicatively coupled to the servicegateway 1336 contained in the data plane VCN 1318.

The untrusted app subnet(s) 1362 can include primary VNICs 1364(1)-(N)that can be communicatively coupled to tenant virtual machines (VMs)1366(1)-(N) residing within the untrusted app subnet(s) 1362. Eachtenant VM 1366(1)-(N) can run code in a respective container 1367(1)-(N)and be communicatively coupled to an app subnet 1326 that can becontained in a data plane app tier 1346 that can be contained in acontainer egress VCN 1368. Respective secondary VNICs 1372(1)-(N) canfacilitate communication between the untrusted app subnet(s) 1362contained in the data plane VCN 1318 and the app subnet contained in thecontainer egress VCN 1368. The container egress VCN can include a NATgateway 1338 that can be communicatively coupled to public Internet 1354(e.g., public Internet 1054 of FIG. 10 ).

The Internet gateway 1334 contained in the control plane VCN 1316 andcontained in the data plane VCN 1318 can be communicatively coupled to ametadata management service 1352 (e.g., the metadata management system1052 of FIG. 10 ) that can be communicatively coupled to public Internet1354. Public Internet 1354 can be communicatively coupled to the NATgateway 1338 contained in the control plane VCN 1316 and contained inthe data plane VCN 1318. The service gateway 1336 contained in thecontrol plane VCN 1316 and contained in the data plane VCN 1318 can becommunicatively couple to cloud services 1356.

In some examples, the pattern illustrated by the architecture of blockdiagram 1300 of FIG. 13 may be considered an exception to the patternillustrated by the architecture of block diagram 1200 of FIG. 12 and maybe desirable for a customer of the IaaS provider if the IaaS providercannot directly communicate with the customer (e.g., a disconnectedregion). The respective containers 1367(1)-(N) that are contained in theVMs 1366(1)-(N) for each customer can be accessed in real-time by thecustomer. The containers 1367(1)-(N) may be configured to make calls torespective secondary VNICs 1372(1)-(N) contained in app subnet(s) 1326of the data plane app tier 1346 that can be contained in the containeregress VCN 1368. The secondary VNICs 1372(1)-(N) can transmit the callsto the NAT gateway 1338 that may transmit the calls to public Internet1354. In this example, the containers 1367(1)-(N) that can be accessedin real-time by the customer can be isolated from the control plane VCN1316 and can be isolated from other entities contained in the data planeVCN 1318. The containers 1367(1)-(N) may also be isolated from resourcesfrom other customers.

In other examples, the customer can use the containers 1367(1)-(N) tocall cloud services 1356. In this example, the customer may run code inthe containers 1367(1)-(N) that requests a service from cloud services1356. The containers 1367(1)-(N) can transmit this request to thesecondary VNICs 1372(1)-(N) that can transmit the request to the NATgateway that can transmit the request to public Internet 1354. PublicInternet 1354 can transmit the request to LB subnet(s) 1322 contained inthe control plane VCN 1316 via the Internet gateway 1334. In response todetermining the request is valid, the LB subnet(s) can transmit therequest to app subnet(s) 1326 that can transmit the request to cloudservices 1356 via the service gateway 1336.

It should be appreciated that IaaS architectures 1000, 1100, 1200, 1300depicted in the figures may have other components than those depicted.Further, the embodiments shown in the figures are only some examples ofa cloud infrastructure system that may incorporate an embodiment of thedisclosure. In some other embodiments, the IaaS systems may have more orfewer components than shown in the figures, may combine two or morecomponents, or may have a different configuration or arrangement ofcomponents.

In certain embodiments, the IaaS systems described herein may include asuite of applications, middleware, and database service offerings thatare delivered to a customer in a self-service, subscription-based,elastically scalable, reliable, highly available, and secure manner. Anexample of such an IaaS system is the Oracle Cloud Infrastructure (OCI)provided by the present assignee.

FIG. 14 illustrates an example computer system 1400, in which variousembodiments may be implemented. The system 1400 may be used to implementany of the computer systems described above. As shown in the figure,computer system 1400 includes a processing unit 1404 that communicateswith a number of peripheral subsystems via a bus subsystem 1402. Theseperipheral subsystems may include a processing acceleration unit 1406,an I/O subsystem 1408, a storage subsystem 1418 and a communicationssubsystem 1424. Storage subsystem 1418 includes tangiblecomputer-readable storage media 1422 and a system memory 1410.

Bus subsystem 1402 provides a mechanism for letting the variouscomponents and subsystems of computer system 1400 communicate with eachother as intended. Although bus subsystem 1402 is shown schematically asa single bus, alternative embodiments of the bus subsystem may utilizemultiple buses. Bus subsystem 1402 may be any of several types of busstructures including a memory bus or memory controller, a peripheralbus, and a local bus using any of a variety of bus architectures. Forexample, such architectures may include an Industry StandardArchitecture (ISA) bus, Micro Channel Architecture (MCA) bus, EnhancedISA (EISA) bus, Video Electronics Standards Association (VESA) localbus, and Peripheral Component Interconnect (PCI) bus, which can beimplemented as a Mezzanine bus manufactured to the IEEE P1386.1standard.

Processing unit 1404, which can be implemented as one or more integratedcircuits (e.g., a conventional microprocessor or microcontroller),controls the operation of computer system 1400. One or more processorsmay be included in processing unit 1404. These processors may includesingle core or multicore processors. In certain embodiments, processingunit 1404 may be implemented as one or more independent processing units1432 and/or 1434 with single or multicore processors included in eachprocessing unit. In other embodiments, processing unit 1404 may also beimplemented as a quad-core processing unit formed by integrating twodual-core processors into a single chip.

In various embodiments, processing unit 1404 can execute a variety ofprograms in response to program code and can maintain multipleconcurrently executing programs or processes. At any given time, some orall of the program code to be executed can be resident in processor(s)1404 and/or in storage subsystem 1418. Through suitable programming,processor(s) 1404 can provide various functionalities described above.Computer system 1400 may additionally include a processing accelerationunit 1406, which can include a digital signal processor (DSP), aspecial-purpose processor, and/or the like.

I/O subsystem 1408 may include user interface input devices and userinterface output devices. User interface input devices may include akeyboard, pointing devices such as a mouse or trackball, a touchpad ortouch screen incorporated into a display, a scroll wheel, a click wheel,a dial, a button, a switch, a keypad, audio input devices with voicecommand recognition systems, microphones, and other types of inputdevices. User interface input devices may include, for example, motionsensing and/or gesture recognition devices such as the Microsoft Kinect®motion sensor that enables users to control and interact with an inputdevice, such as the Microsoft Xbox® 360 game controller, through anatural user interface using gestures and spoken commands. Userinterface input devices may also include eye gesture recognition devicessuch as the Google Glass® blink detector that detects eye activity(e.g., ‘blinking’ while taking pictures and/or making a menu selection)from users and transforms the eye gestures as input into an input device(e.g., Google Glass®). Additionally, user interface input devices mayinclude voice recognition sensing devices that enable users to interactwith voice recognition systems (e.g., Siri® navigator), through voicecommands.

User interface input devices may also include, without limitation, threedimensional (3D) mice, joysticks or pointing sticks, gamepads andgraphic tablets, and audio/visual devices such as speakers, digitalcameras, digital camcorders, portable media players, webcams, imagescanners, fingerprint scanners, barcode reader 3D scanners, 3D printers,laser rangefinders, and eye gaze tracking devices. Additionally, userinterface input devices may include, for example, medical imaging inputdevices such as computed tomography, magnetic resonance imaging,position emission tomography, medical ultrasonography devices. Userinterface input devices may also include, for example, audio inputdevices such as MIDI keyboards, digital musical instruments and thelike.

User interface output devices may include a display subsystem, indicatorlights, or non-visual displays such as audio output devices, etc. Thedisplay subsystem may be a cathode ray tube (CRT), a flat-panel device,such as that using a liquid crystal display (LCD) or plasma display, aprojection device, a touch screen, and the like. In general, use of theterm “output device” is intended to include all possible types ofdevices and mechanisms for outputting information from computer system1400 to a user or other computer. For example, user interface outputdevices may include, without limitation, a variety of display devicesthat visually convey text, graphics and audio/video information such asmonitors, printers, speakers, headphones, automotive navigation systems,plotters, voice output devices, and modems.

Computer system 1400 may comprise a storage subsystem 1418 that providesa tangible non-transitory computer-readable storage medium for storingsoftware and data constructs that provide the functionality of theembodiments described in this disclosure. The software can includeprograms, code modules, instructions, scripts, etc., that when executedby one or more cores or processors of processing unit 1404 provide thefunctionality described above. Storage subsystem 1418 may also provide arepository for storing data used in accordance with the presentdisclosure.

As depicted in the example in FIG. 14 , storage subsystem 1418 caninclude various components including a system memory 1410,computer-readable storage media 1422, and a computer readable storagemedia reader 1420. System memory 1410 may store program instructionsthat are loadable and executable by processing unit 1404. System memory1410 may also store data that is used during the execution of theinstructions and/or data that is generated during the execution of theprogram instructions. Various different kinds of programs may be loadedinto system memory 1410 including but not limited to clientapplications, Web browsers, mid-tier applications, relational databasemanagement systems (RDBMS), virtual machines, containers, etc.

System memory 1410 may also store an operating system 1416. Examples ofoperating system 1416 may include various versions of MicrosoftWindows®, Apple Macintosh®, and/or Linux operating systems, a variety ofcommercially-available UNIX® or UNIX-like operating systems (includingwithout limitation the variety of GNU/Linux operating systems, theGoogle Chrome® OS, and the like) and/or mobile operating systems such asiOS, Windows® Phone, Android® OS, BlackBerry® OS, and Palm® OS operatingsystems. In certain implementations where computer system 1400 executesone or more virtual machines, the virtual machines along with theirguest operating systems (GOSs) may be loaded into system memory 1410 andexecuted by one or more processors or cores of processing unit 1404.

System memory 1410 can come in different configurations depending uponthe type of computer system 1400. For example, system memory 1410 may bevolatile memory (such as random access memory (RAM)) and/or non-volatilememory (such as read-only memory (ROM), flash memory, etc.) Differenttypes of RAM configurations may be provided including a static randomaccess memory (SRAM), a dynamic random access memory (DRAM), and others.In some implementations, system memory 1410 may include a basicinput/output system (BIOS) containing basic routines that help totransfer information between elements within computer system 1400, suchas during start-up.

Computer-readable storage media 1422 may represent remote, local, fixed,and/or removable storage devices plus storage media for temporarilyand/or more permanently containing, storing, computer-readableinformation for use by computer system 1400 including instructionsexecutable by processing unit 1404 of computer system 1400.

Computer-readable storage media 1422 can include any appropriate mediaknown or used in the art, including storage media and communicationmedia, such as but not limited to, volatile and non-volatile, removableand non-removable media implemented in any method or technology forstorage and/or transmission of information. This can include tangiblecomputer-readable storage media such as RAM, ROM, electronicallyerasable programmable ROM (EEPROM), flash memory or other memorytechnology, CD-ROM, digital versatile disk (DVD), or other opticalstorage, magnetic cassettes, magnetic tape, magnetic disk storage orother magnetic storage devices, or other tangible computer readablemedia.

By way of example, computer-readable storage media 1422 may include ahard disk drive that reads from or writes to non-removable, nonvolatilemagnetic media, a magnetic disk drive that reads from or writes to aremovable, nonvolatile magnetic disk, and an optical disk drive thatreads from or writes to a removable, nonvolatile optical disk such as aCD ROM, DVD, and Blu-Ray® disk, or other optical media.Computer-readable storage media 1422 may include, but is not limited to,Zip® drives, flash memory cards, universal serial bus (USB) flashdrives, secure digital (SD) cards, DVD disks, digital video tape, andthe like. Computer-readable storage media 1422 may also include,solid-state drives (SSD) based on non-volatile memory such asflash-memory based SSDs, enterprise flash drives, solid state ROM, andthe like, SSDs based on volatile memory such as solid state RAM, dynamicRAM, static RAM, DRAM-based SSDs, magnetoresistive RAM (MRAM) SSDs, andhybrid SSDs that use a combination of DRAM and flash memory based SSDs.The disk drives and their associated computer-readable media may providenon-volatile storage of computer-readable instructions, data structures,program modules, and other data for computer system 1400.

Machine-readable instructions executable by one or more processors orcores of processing unit 1404 may be stored on a non-transitorycomputer-readable storage medium. A non-transitory computer-readablestorage medium can include physically tangible memory or storage devicesthat include volatile memory storage devices and/or non-volatile storagedevices. Examples of non-transitory computer-readable storage mediuminclude magnetic storage media (e.g., disk or tapes), optical storagemedia (e.g., DVDs, CDs), various types of RAM, ROM, or flash memory,hard drives, floppy drives, detachable memory drives (e.g., USB drives),or other type of storage device.

Communications subsystem 1424 provides an interface to other computersystems and networks. Communications subsystem 1424 serves as aninterface for receiving data from and transmitting data to other systemsfrom computer system 1400. For example, communications subsystem 1424may enable computer system 1400 to connect to one or more devices viathe Internet. In some embodiments communications subsystem 1424 caninclude radio frequency (RF) transceiver components for accessingwireless voice and/or data networks (e.g., using cellular telephonetechnology, advanced data network technology, such as 3G, 4G or EDGE(enhanced data rates for global evolution), WiFi (IEEE 802.11 familystandards, or other mobile communication technologies, or anycombination thereof), global positioning system (GPS) receivercomponents, and/or other components. In some embodiments communicationssubsystem 1424 can provide wired network connectivity (e.g., Ethernet)in addition to or instead of a wireless interface.

In some embodiments, communications subsystem 1424 may also receiveinput communication in the form of structured and/or unstructured datafeeds 1426, event streams 1428, event updates 1430, and the like onbehalf of one or more users who may use computer system 1400.

By way of example, communications subsystem 1424 may be configured toreceive data feeds 1426 in real-time from users of social networksand/or other communication services such as Twitter® feeds, Facebook®updates, web feeds such as Rich Site Summary (RSS) feeds, and/orreal-time updates from one or more third party information sources.

Additionally, communications subsystem 1424 may also be configured toreceive data in the form of continuous data streams, which may includeevent streams 1428 of real-time events and/or event updates 1430, thatmay be continuous or unbounded in nature with no explicit end. Examplesof applications that generate continuous data may include, for example,sensor data applications, financial tickers, network performancemeasuring tools (e.g., network monitoring and traffic managementapplications), clickstream analysis tools, automobile trafficmonitoring, and the like.

Communications subsystem 1424 may also be configured to output thestructured and/or unstructured data feeds 1426, event streams 1428,event updates 1430, and the like to one or more databases that may be incommunication with one or more streaming data source computers coupledto computer system 1400.

Computer system 1400 can be one of various types, including a handheldportable device (e.g., an iPhone® cellular phone, an iPad® computingtablet, a PDA), a wearable device (e.g., a Google Glass® head mounteddisplay), a PC, a workstation, a mainframe, a kiosk, a server rack, orany other data processing system.

Due to the ever-changing nature of computers and networks, thedescription of computer system 1400 depicted in the figure is intendedonly as a specific example. Many other configurations having more orfewer components than the system depicted in the figure are possible.For example, customized hardware might also be used and/or particularelements might be implemented in hardware, firmware, software (includingapplets), or a combination. Further, connection to other computingdevices, such as network input/output devices, may be employed. Based onthe disclosure and teachings provided herein, a person of ordinary skillin the art will appreciate other ways and/or methods to implement thevarious embodiments.

Although specific embodiments have been described, variousmodifications, alterations, alternative constructions, and equivalentsare also encompassed within the scope of the disclosure. Embodiments arenot restricted to operation within certain specific data processingenvironments but are free to operate within a plurality of dataprocessing environments. Additionally, although embodiments have beendescribed using a particular series of transactions and steps, it shouldbe apparent to those skilled in the art that the scope of the presentdisclosure is not limited to the described series of transactions andsteps. Various features and aspects of the above-described embodimentsmay be used individually or jointly.

Further, while embodiments have been described using a particularcombination of hardware and software, it should be recognized that othercombinations of hardware and software are also within the scope of thepresent disclosure. Embodiments may be implemented only in hardware, oronly in software, or using combinations thereof. The various processesdescribed herein can be implemented on the same processor or differentprocessors in any combination. Accordingly, where components or modulesare described as being configured to perform certain operations, suchconfiguration can be accomplished, e.g., by designing electroniccircuits to perform the operation, by programming programmableelectronic circuits (such as microprocessors) to perform the operation,or any combination thereof. Processes can communicate using a variety oftechniques including but not limited to conventional techniques forinter process communication, and different pairs of processes may usedifferent techniques, or the same pair of processes may use differenttechniques at different times.

The specification and drawings are, accordingly, to be regarded in anillustrative rather than a restrictive sense. It will, however, beevident that additions, subtractions, deletions, and other modificationsand changes may be made thereunto without departing from the broaderspirit and scope as set forth in the claims. Thus, although specificdisclosure embodiments have been described, these are not intended to belimiting. Various modifications and equivalents are within the scope ofthe following claims.

The use of the terms “a” and “an” and “the” and similar referents in thecontext of describing the disclosed embodiments (especially in thecontext of the following claims) are to be construed to cover both thesingular and the plural, unless otherwise indicated herein or clearlycontradicted by context. The terms “comprising,” “having,” “including,”and “containing” are to be construed as open-ended terms (i.e., meaning“including, but not limited to,”) unless otherwise noted. The term“connected” is to be construed as partly or wholly contained within,attached to, or joined together, even if there is something intervening.Recitation of ranges of values herein are merely intended to serve as ashorthand method of referring individually to each separate valuefalling within the range, unless otherwise indicated herein and eachseparate value is incorporated into the specification as if it wereindividually recited herein. All methods described herein can beperformed in any suitable order unless otherwise indicated herein orotherwise clearly contradicted by context. The use of any and allexamples, or exemplary language (e.g., “such as”) provided herein, isintended merely to better illuminate embodiments and does not pose alimitation on the scope of the disclosure unless otherwise claimed. Nolanguage in the specification should be construed as indicating anynon-claimed element as essential to the practice of the disclosure.

Disjunctive language such as the phrase “at least one of X, Y, or Z,”unless specifically stated otherwise, is intended to be understoodwithin the context as used in general to present that an item, term,etc., may be either X, Y, or Z, or any combination thereof (e.g., X, Y,and/or Z). Thus, such disjunctive language is not generally intended to,and should not, imply that certain embodiments require at least one ofX, at least one of Y, or at least one of Z to each be present.

Preferred embodiments of this disclosure are described herein, includingthe best mode known for carrying out the disclosure. Variations of thosepreferred embodiments may become apparent to those of ordinary skill inthe art upon reading the foregoing description. Those of ordinary skillshould be able to employ such variations as appropriate and thedisclosure may be practiced otherwise than as specifically describedherein. Accordingly, this disclosure includes all modifications andequivalents of the subject matter recited in the claims appended heretoas permitted by applicable law. Moreover, any combination of theabove-described elements in all possible variations thereof isencompassed by the disclosure unless otherwise indicated herein.

All references, including publications, patent applications, andpatents, cited herein are hereby incorporated by reference to the sameextent as if each reference were individually and specifically indicatedto be incorporated by reference and were set forth in its entiretyherein.

In the foregoing specification, aspects of the disclosure are describedwith reference to specific embodiments thereof, but those skilled in theart will recognize that the disclosure is not limited thereto. Variousfeatures and aspects of the above-described disclosure may be usedindividually or jointly. Further, embodiments can be utilized in anynumber of environments and applications beyond those described hereinwithout departing from the broader spirit and scope of thespecification. The specification and drawings are, accordingly, to beregarded as illustrative rather than restrictive.

What is claimed is:
 1. A computer-implemented method, comprising:obtaining, by an orchestration service of a cloud-computing environment,a plurality of configuration files corresponding to a plurality ofservices to be bootstrapped to a region, the plurality of configurationfiles providing data from which bootstrapping tasks for bootstrappingthe plurality of services within the region are identifiable;identifying, by the orchestration service, one or more dependenciesbetween respective services of the plurality of services based at leastin part on executing operations for parsing the plurality ofconfiguration files; generating, based at least in part on the parsing,a build dependency graph that maintains the one or more dependenciesidentified, the build dependency graph being a data structure thatidentifies the plurality of configuration files and the one or moredependencies and indicates a corresponding order with whichbootstrapping tasks are to be performed; and incrementally instructing,by the orchestration service, a provisioning and deployment manager toexecute bootstrapping tasks based at least in part on traversing thebuild dependency graph, the bootstrapping tasks being executed to causethe plurality of services to be bootstrapped to the region according tothe one or more dependencies identified.
 2. The computer-implementedmethod of claim 1, wherein identifying the one or more dependenciesfurther comprises: identifying, by the orchestration service and basedat least in part on the parsing, a required capability of a firstservice on which a second service depends, wherein the build dependencygraph as generated indicates that the first service is to bebootstrapped before the second service and that initiation of respectivebootstrapping tasks for the second service is to be delayed until acapability indicating the first service is bootstrapped is published. 3.The computer-implemented method of claim 2, wherein identifying the oneor more dependencies further comprises: identifying, by theorchestration service and based at least in part on the parsing, anoptional capability of the first service on which a second serviceoptionally depends, wherein the build dependency graph as generatedindicates that the second service may be bootstrapped before the firstservice.
 4. The computer-implemented method of claim 3, wherein thebuild dependency graph further indicates that, if the second service isbootstrapped before the first service, additional bootstrapping taskscorresponding to the second service are to be executed when the firstservice is available.
 5. The computer-implemented method of claim 1,further comprising: identifying, by the orchestration service, acircular dependency between two services, wherein identifying thecircular dependency causes the orchestration service to instruct theprovisioning and deployment manager to perform at least one additionalexecution of respective bootstrapping tasks corresponding to at leastone of the two services, whereby performing the at least one additionalexecution of the respective bootstrapping tasks resolved the circulardependency between the two services.
 6. The computer-implemented methodof claim 1, further comprising identifying, by the orchestrationservice, an orphaned service within the build dependency graph, thebuild dependency graph indicating that the orphaned service will not bebootstrapped due to an error with a corresponding configuration filecorresponding to the orphaned service.
 7. The computer-implementedmethod of claim 1, further comprising generating, by the orchestrationservice, a plurality of phase data structures identifying one or morephases associated with bootstrapping the region and an order by whichthe one or more phases are to be executed, each phase being associatedwith bootstrapping one or more instances of a given service.
 8. Acomputing system comprising: one or more processors; and one or morememories storing computer-executable instructions that, when executed bythe one or more processors, causes an orchestration service of thecomputing system to: obtain a plurality of configuration filescorresponding to a plurality of services to be bootstrapped to a region,the plurality of configuration files providing data from whichbootstrapping tasks for bootstrapping the plurality of services withinthe region are identifiable; identify one or more dependencies betweenrespective services of the plurality of services based at least in parton executing operations for parsing the plurality of configurationfiles; generate, based at least in part on the parsing, a builddependency graph that maintains the one or more dependencies identified,the build dependency graph being a data structure that identifies theplurality of configuration files and the one or more dependencies andindicates a corresponding order with which bootstrapping tasks are to beperformed; and incrementally instruct a provisioning and deploymentmanager to execute bootstrapping tasks based at least in part ontraversing the build dependency graph, the bootstrapping tasks beingexecuted to cause the plurality of services to be bootstrapped to theregion according to the one or more dependencies identified.
 9. Thecomputing system of claim 8, wherein executing the computer-executableinstructions for identifying the one or more dependencies, furthercauses the orchestration service to: identify, based at least in part onthe parsing, a required capability of a first service on which a secondservice depends, wherein the build dependency graph as generatedindicates that the first service is to be bootstrapped before the secondservice and that initiation of respective bootstrapping tasks for thesecond service is to be delayed until a capability indicating the firstservice is bootstrapped is published.
 10. The computing system of claim9, wherein executing the computer-executable instructions foridentifying the one or more dependencies, further causes theorchestration service to: identify, based at least in part on theparsing, an optional capability of the first service on which a secondservice optionally depends, wherein the build dependency graph asgenerated indicates that the second service may be bootstrapped beforethe first service.
 11. The computing system of claim 10, wherein thebuild dependency graph further indicates that, if the second service isbootstrapped before the first service, additional bootstrapping taskscorresponding to the second service are to be executed when the firstservice is available.
 12. The computing system of claim 8, whereinexecuting the computer-executable instructions further causes theorchestration service to: identifying a circular dependency between twoservices, wherein identifying the circular dependency causes theorchestration service to instruct the provisioning and deploymentmanager to perform at least one additional execution of respectivebootstrapping tasks corresponding to at least one of the two services,whereby performing the at least one additional execution of therespective bootstrapping tasks resolved the circular dependency betweenthe two services.
 13. The computing system of claim 8, wherein executingthe computer-executable instructions further causes the orchestrationservice to identify an orphaned service within the build dependencygraph, the build dependency graph indicating that the orphaned servicewill not be bootstrapped due to an error with a correspondingconfiguration file corresponding to the orphaned service.
 14. Thecomputing system of claim 8, wherein executing the computer-executableinstructions further causes the orchestration service to generate aplurality of phase data structures identifying one or more phasesassociated with bootstrapping the region and an order by which the oneor more phases are to be executed, each phase being associated withbootstrapping one or more instances of a given service.
 15. Anon-transitory computer-readable storage medium storingcomputer-executable instructions that, when executed by one or moreprocessors, causes an orchestration service of a cloud-computing systemto: obtain a plurality of configuration files corresponding to aplurality of services to be bootstrapped to a region, the plurality ofconfiguration files providing data from which bootstrapping tasks forbootstrapping the plurality of services within the region areidentifiable; identify one or more dependencies between respectiveservices of the plurality of services based at least in part onexecuting operations for parsing the plurality of configuration files;generate, based at least in part on the parsing, a build dependencygraph that maintains the one or more dependencies identified, the builddependency graph being a data structure that identifies the plurality ofconfiguration files and the one or more dependencies and indicates acorresponding order with which bootstrapping tasks are to be performed;and incrementally instruct a provisioning and deployment manager toexecute bootstrapping tasks based at least in part on traversing thebuild dependency graph, the bootstrapping tasks being executed to causethe plurality of services to be bootstrapped to the region according tothe one or more dependencies identified.
 16. The non-transitorycomputer-readable storage medium of claim 15, wherein executing thecomputer-executable instructions for identifying the one or moredependencies, further causes the orchestration service to: identify,based at least in part on the parsing, a required capability of a firstservice on which a second service depends, wherein the build dependencygraph as generated indicates that the first service is to bebootstrapped before the second service and that initiation of respectivebootstrapping tasks for the second service is to be delayed until acapability indicating the first service is bootstrapped is published.17. The non-transitory computer-readable storage medium of claim 16,wherein executing the computer-executable instructions for identifyingthe one or more dependencies, further causes the orchestration serviceto: identify, based at least in part on the parsing, an optionalcapability of the first service on which a second service optionallydepends, wherein the build dependency graph as generated indicates thatthe second service may be bootstrapped before the first service.
 18. Thenon-transitory computer-readable storage medium of claim 15, whereinexecuting the computer-executable instructions further causes theorchestration service to: identifying a circular dependency between twoservices, wherein identifying the circular dependency causes theorchestration service to instruct the provisioning and deploymentmanager to perform at least one additional execution of respectivebootstrapping tasks corresponding to at least one of the two services,whereby performing the at least one additional execution of therespective bootstrapping tasks resolved the circular dependency betweenthe two services.
 19. The non-transitory computer-readable storagemedium of claim 15, wherein executing the computer-executableinstructions further causes the orchestration service to identify anorphaned service within the build dependency graph, the build dependencygraph indicating that the orphaned service will not be bootstrapped dueto an error with a corresponding configuration file corresponding to theorphaned service.
 20. The non-transitory computer-readable storagemedium of claim 15, wherein executing the computer-executableinstructions further causes the orchestration service to generate aplurality of phase data structures identifying one or more phasesassociated with bootstrapping the region and an order by which the oneor more phases are to be executed, each phase being associated withbootstrapping one or more instances of a given service.